fix: JSON import type assertion

[SheetJSDev]

🔗 Linked issue

#1823

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

See linked issue

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly. (n/a)

[netlify]

✅ Deploy Preview for nuxt-content ready!

Name	Link
🔨 Latest commit	4e6292d
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-content/deploys/63c95056178c8500082e16e0
😎 Deploy Preview	https://deploy-preview-1824--nuxt-content.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[HigherOrderLogic]

 WARN  rollup-plugin-inject: failed to parse /node_modules/@nuxt/content/dist/runtime/transformers/shiki/highlighter.mjs. Consider restricting the plugin to particular files via options.include           

 ERROR                                                                                                                                                                                                           

2: import consola from "consola";
3: import { createSingleton } from "../utils.mjs";
4: import mdcTMLanguage from "./languages/mdc.tmLanguage.json" assert { type: "json" };
                                                               ^
5: const logger = consola.withScope("@nuxt/content");
6: const resolveLang = (lang) => BUNDLED_LANGUAGES.find((l) => l.id === lang || l.aliases?.includes(lang))?.id || lang;

Do you get this error?

[SheetJSDev]

That error shows up but oddly enough the pages are still built locally. This patch was the obvious one to resolve the esbuild issue.

There is a bypass without patching the library: change the defineTransformer import to use the version in utils. This change would be applied to the transformer script:

-import { defineTransformer } from '@nuxt/content/transformers'
+import { defineTransformer } from '@nuxt/content/transformers/utils'

[HigherOrderLogic]

That error shows up but oddly enough the pages are still built locally. This patch was the obvious one to resolve the esbuild issue.

There is a bypass without patching the library: change the defineTransformer import to use the version in utils. This change would be applied to the transformer script:

-import { defineTransformer } from '@nuxt/content/transformers'
+import { defineTransformer } from '@nuxt/content/transformers/utils'

Thanks for the workaround.

[farnabaz]

Import assertion is only supported in Node.js 17 or later (ref). And most of the users still use v16.

[farnabaz]

Let's convert the json file into a JavaScript one. This will resolve the issue.

@pi0 WDYT?

[SheetJSDev]

That approach is better. Patch updated.

There were type issues which prevented the use of the official IRawGrammar type, mainly around comments. For example:

{
  "repository": {
    "block": {
      "comment": "Same as `text.html.markdown#block`, but without `raw_block`",

Based on its usage:

• the root object should be IRawGrammar
• repository should be an object of type IRawRepository
• block should be an object of type IRawRule.

Neither IRawRule nor its parent type ILocatable have a comment field. It's unclear whether this oversight is a bug in vscode-textmate or if it should be removed here.

[farnabaz]

Thanks