mdsvex@0.9.7

Patch Changes

• #265 d1c1b4f Thanks @wlach! - Escape code chunks in browser builds

mdsvex@0.9.6

Patch Changes

• #256 492b7a4 Thanks @pngwn! - Props passed to mdsvex documents will now be forwarded to layout files.

mdsvex@0.9.5

Patch Changes

• #253 8dc7900 Thanks @pngwn! - There is now an ESM browser build in addition to UMD.

mdsvex@0.9.4

Patch Changes

• #251 3d8b400 Thanks @pngwn! - UMD build now works in the browser.

mdsvex@0.9.3

Patch Changes

• 2af50ee #239 Thanks @brev! - Standalone compile() function not returning headmatter attributes. Also export all types.

mdsvex@0.9.2

Patch Changes

• 0567e15 #237 Thanks @pngwn! - Fix "Cannot find module 'prism-svelte'" error.

mdsvex@0.9.1

Patch Changes

• f458229 #234 Thanks @pngwn! - mdsvex now exposes an escapeSvelte utility to help with escaping Svelte syntax in custom highlight functions.

• fe9b437 #233 Thanks @pngwn! - Language definitions for fenced code-blocks are now case insensitive.

• 8c905ce #231 Thanks @pngwn! - Svelte syntax is now highlighted by default when using the default code highlighter.

mdsvex@0.9.0

Minor Changes

• 99da8fe #207 Thanks @pngwn! - User-provided remark plugins that modify code nodes now run before the builtin in code highlighting, allowing for custom code transformations.

• aa8d825 #209 Thanks @pngwn! - Asynchronous custom highlight functions are now supported.

svelte-parse@0.1.0

Minor Changes

• b5b526e #198 Thanks @pngwn! - Add a new SVAST node SvelteDynamicContent in order to disambiguate positions of expressions due to them not always having opening and closing braces(#174).

  Ensure that unquoted attribute values are correctly parsed as separate values where appropriate(#178).

Patch Changes

• Updated dependencies [b5b526e]:
  • svast@0.2.0

svast@0.2.0

Minor Changes

• b5b526e #198 Thanks @pngwn! - Add a new SVAST node SvelteDynamicContent in order to disambiguate positions of expressions due to them not always having opening and closing braces(#174).

  Ensure that unquoted attribute values are correctly parsed as separate values where appropriate(#178).