chore: release vscode-mdx

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

[email protected]

Minor Changes

• #226 0fdf371 Thanks @remcohaszing! - Add experimental IntelliSense

  To enable IntelliSense, set mdx.experimentalLanguageServer to true in your
  VSCode settings.
  You can verify it’s enabled by interacting with the JavaScript parts on an MDX
  document, for example by hovering an import or variable

• #222 d2eb7a7 Thanks @KeyboardSounds! - Support for highlighting JSX evaluated expressions

  In JSX, you can include JS expressions within tags, like:

  <Component>{doSomething('a', 7)}</Component>

  This PR adds syntax highlighting for those expressions by adding a new pattern
  in the tmLanguage.json.

[wooorm]

hmm

[remcohaszing]

Let’s get this merged!

I guess this will automagically create a release? We’ll see.

[wooorm]

Would be good to create a GH release as well (https://github.com/mdx-js/vscode-mdx/releases)

[remcohaszing]

I think it should, based on tags, but no tag is created.

[remcohaszing]

I’ll create a tag manually.

[remcohaszing]

Ok, so there are some quirks to resolve:

• Changesets creates a release PR
• A tag should be created (created manually)
• A tag should create a release (created manually)
• A release should
  • Package the extension
  • Publish to VSCode marketplace
  • Publish to OpenVSX
  • Attach built package to release

So it is published now, but it needs some streamlining. Also packages need to be published eventually.

[remcohaszing]

https://twitter.com/remcohaszing/status/1613910319805382657