@astrojs/markdoc 0.5.0-rc.1 → 0.5.1

package/README.md

@@ -42,15 +42,15 @@ npm install @astrojs/markdoc
 
 Then, apply this integration to your `astro.config.*` file using the `integrations` property:
 
-```js ins={3} "markdoc()"
-// astro.config.mjs
-import { defineConfig } from 'astro/config';
-import markdoc from '@astrojs/markdoc';
-
-export default defineConfig({
-  // ...
-  integrations: [markdoc()],
-});
+```diff lang="js" "markdoc()"
+  // astro.config.mjs
+  import { defineConfig } from 'astro/config';
++ import markdoc from '@astrojs/markdoc';
+  export default defineConfig({
+    // ...
+    integrations: [markdoc()],
+    //             ^^^^^^^^^
+  });
 ```
 
 ### Editor Integration
@@ -344,6 +344,36 @@ Now, you can call this function from any Markdoc content entry:
 
 📚 [See the Markdoc documentation](https://markdoc.dev/docs/functions#creating-a-custom-function) for more on using variables or functions in your content.
 
+### Markdoc Language Server
+
+If you are using VS Code, there is an official [Markdoc language extension](https://marketplace.visualstudio.com/items?itemName=Stripe.markdoc-language-support) that includes syntax highlighting and autocomplete for configured tags. [See the language server on GitHub](https://github.com/markdoc/language-server.git) for more information.
+
+To set up the extension, create a `markdoc.config.json` file into the project root with following content:
+
+```json
+[
+  {
+    "id": "my-site",
+    "path": "src/content",
+    "schema": {
+      "path": "markdoc.config.mjs",
+      "type": "esm",
+      "property": "default",
+      "watch": true
+    }
+  }
+]
+```
+
+The `schema` property contains all information to configure the language server for Astro content collections. It accepts following properties:
+
+- `path`: The path to the configuration file.
+- `type`: The type of module your configuration file uses (`esm` allows `import` syntax).
+- `property`: The exported property name that contains the configuration object.
+- `watch`: Tell the server to watch for changes in the configuration.
+
+The top-level `path` property tells the server where content is located. Since Markdoc is specific to content collections, you can use `src/content`.
+
 ### Pass Markdoc variables
 
 You may need to pass [variables][markdoc-variables] to your content. This is useful when passing SSR parameters like A/B tests.
@@ -413,15 +443,16 @@ By default, Markdoc will not recognize HTML markup as semantic content.
 
 To achieve a more Markdown-like experience, where HTML elements can be included alongside your content, set `allowHTML:true` as a `markdoc` integration option. This will enable HTML parsing in Markdoc markup.
 
-```js {7} "allowHTML: true"
-// astro.config.mjs
-import { defineConfig } from 'astro/config';
-import markdoc from '@astrojs/markdoc';
+```diff lang="js" "allowHTML: true"
+  // astro.config.mjs
+  import { defineConfig } from 'astro/config';
+  import markdoc from '@astrojs/markdoc';
 
-export default defineConfig({
-  // ...
-  integrations: [markdoc({ allowHTML: true })],
-});
+  export default defineConfig({
+    // ...
++   integrations: [markdoc({ allowHTML: true })],
+    //                       ^^^^^^^^^^^^^^^
+  });
 ```
 
 > **Warning**

package/components/TreeNode.ts

@@ -92,14 +92,11 @@ export const ComponentNode = createComponent({
 			// `result.propagators` has been moved to `result._metadata.propagators`
 			// TODO: remove this fallback in the next markdoc integration major
 			const propagators = result._metadata.propagators || result.propagators;
-			propagators.set(
-				{},
-				{
-					init() {
-						return headAndContent;
-					},
-				}
-			);
+			propagators.add({
+				init() {
+					return headAndContent;
+				},
+			});
 
 			return headAndContent;
 		}

package/dist/html/index.d.ts

@@ -1,2 +1,2 @@
-export { htmlTag } from './tagdefs/html.tag';
-export { htmlTokenTransform } from './transform/html-token-transform';
+export { htmlTag } from './tagdefs/html.tag.js';
+export { htmlTokenTransform } from './transform/html-token-transform.js';

package/dist/html/index.js

@@ -1,5 +1,5 @@
-import { htmlTag } from "./tagdefs/html.tag";
-import { htmlTokenTransform } from "./transform/html-token-transform";
+import { htmlTag } from "./tagdefs/html.tag.js";
+import { htmlTokenTransform } from "./transform/html-token-transform.js";
 export {
   htmlTag,
   htmlTokenTransform

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@astrojs/markdoc",
   "description": "Add support for Markdoc in your Astro site",
-  "version": "0.5.0-rc.1",
+  "version": "0.5.1",
   "type": "module",
   "types": "./dist/index.d.ts",
   "author": "withastro",
@@ -57,32 +57,32 @@
   ],
   "dependencies": {
     "@markdoc/markdoc": "^0.3.0",
-    "esbuild": "^0.18.16",
+    "esbuild": "^0.19.2",
     "github-slugger": "^2.0.0",
     "gray-matter": "^4.0.3",
     "htmlparser2": "^9.0.0",
     "kleur": "^4.1.5",
-    "shiki": "^0.14.1",
-    "zod": "^3.17.3",
-    "@astrojs/internal-helpers": "0.2.0-rc.2",
-    "@astrojs/prism": "3.0.0-rc.1"
+    "shiki": "^0.14.3",
+    "zod": "3.21.1",
+    "@astrojs/internal-helpers": "0.2.0",
+    "@astrojs/prism": "3.0.0"
   },
   "peerDependencies": {
-    "astro": "^3.0.0-rc.5"
+    "astro": "^3.2.2"
   },
   "devDependencies": {
     "@types/chai": "^4.3.5",
     "@types/html-escaper": "^3.0.0",
-    "@types/markdown-it": "^12.2.3",
-    "@types/mocha": "^9.1.1",
+    "@types/markdown-it": "^13.0.0",
+    "@types/mocha": "^10.0.1",
     "chai": "^4.3.7",
     "devalue": "^4.3.2",
-    "linkedom": "^0.14.26",
-    "mocha": "^9.2.2",
-    "rollup": "^3.25.1",
-    "vite": "^4.4.6",
-    "@astrojs/markdown-remark": "3.0.0-rc.1",
-    "astro": "3.0.0-rc.5",
+    "linkedom": "^0.15.1",
+    "mocha": "^10.2.0",
+    "rollup": "^3.28.1",
+    "vite": "^4.4.9",
+    "@astrojs/markdown-remark": "3.2.0",
+    "astro": "3.2.2",
     "astro-scripts": "0.0.14"
   },
   "engines": {