building for different swc versions

[souporserious]

Hello, I'm having trouble using this in Next.js and assuming it is version-related like mentioned in the readme. I pulled down the library and built the wasm file, but it did not work. I also tried rolling back to a previous Next.js canary like the SWC docs mentioned, which loaded instead of crashing, but does not seem to work still. Please see the reproduction here.

I'm happy to help try out a PR to get newer versions to work, just not sure how best to contribute since I'm new to Rust still 😇

[jcoon97]

👋 The current version that's released is built against swc_core v0.74.*, which only works with @swc/core v1.3.44 ~ v1.3.47. Looking at the compatibility page, it looks like that @swc/core range would fall under Next v13.2.4 ~ v13.3.1, which unfortunately had an issue with loading Wasm plugins.

As far as I'm aware, Next v13.3.2+ should now be able to load SWC plugins; however, building the plugin against swc_core v0.75.* causes the plugin to panic when calling get_context.

I plan on filling out a bug report on the SWC repository for them to investigate, and will build/publish an update to the plugin once that's been resolved!

For an example of using the plugin with @swc/core v1.3.44 ~ v1.3.47, I've created this environment over on CodeSandbox. Though it doesn't make use of Next's integration with SWC (it uses @swc/core instead), hopefully the plugin will integrate with Next once we're able to build against swc_core v0.75.* in the near future.

[souporserious]

Ah, good to know, I appreciate the insight and the example! I was getting the panic as well and didn't realize it was a bug causing it.

Thank you for this plugin btw! I started building my own pipeline through esbuild for docs when I realized I just needed to be able to glob MDX files and came across your package.