Matching Versions (Plugin Development)

[stahlbauer]

Hi. I am developing a plugin with version "0.69.30" of SWC core. Which version of the NodeJS package is supposed to work with it?

[stahlbauer]

To be more concrete: I am facing the following runtime error:

Caused by:
    0: Failed to create plugin instance
    1: Error while importing "__wbindgen_placeholder__"."__wbindgen_describe": unknown import. Expected Function(FunctionType { params: [I32], results: [] })', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/swc-0.255.18/src/plugin.rs:228:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

while everything seems to build without any errors.

[kdy1]

Also, "__wbindgen_placeholder__"."__wbindgen_describe" is not related to swc at all. I think it's a bug related to the wasm-pack, but I'm not sure.

[stahlbauer]

@kwonoj What is the reason you are using wasm-pack for swc-plugin-coverage-instrument?

[stahlbauer]

(this would also be interesting for the docs on writing plugins)

[kwonoj]

I don't use wasm-pack for the coverage plugin except test only fixture setup.

[stahlbauer]

Ok, thanks. Was wondering because the WASM created from my plugin has wbindgen placeholder functions. See, for example,

  Functions:
    "env"."__emit_diagnostics": [I32, I32] -> []
    "env"."__set_transform_result": [I32, I32] -> []
    "env"."__set_transform_plugin_core_pkg_diagnostics": [I32, I32] -> []
    "__wbindgen_placeholder__"."__wbindgen_is_undefined": [I32] -> [I32]
    "__wbindgen_placeholder__"."__wbindgen_in": [I32, I32] -> [I32]
    "__wbindgen_placeholder__"."__wbindgen_boolean_get": [I32] -> [I32]

[timofei-iatsenko]

https://swc.rs/docs/plugin/selecting-swc-core

[stahlbauer]

Thanks for the pointer; does not fix my problem, so far. I have tried different version combis.

For the plugin (Cargo.toml):

swc = { version = "0.255.3" }
swc_core = {version = "0.69.30", features = [

For using the plugin (package.json):

    "@swc/core": "1.3.40",

[stahlbauer]

The plugin is called as follows:

	return swc.transformSync(sourceContent, {
		filename: sourceFilename,
		sourceMaps: true,
		inlineSourcesContent: false,
		minify: false,
		isModule: true,
		jsc: {
			experimental: {
				plugins: [['TheNameOfMyPlugin', pluginOptions]]
			}
		}
	});

By removing the plugin, the error vanishes. But this is not the goal of this exercise :-D

[stahlbauer]

The signature of my plugin looks as follows:

#[plugin_transform]
pub fn process_transform(
    mut program: Program,
    metadata: TransformPluginProgramMetadata,
) -> Program {

The plugin is built using cargo build --target wasm32-wasi.

[timofei-iatsenko]

it seems there an issue in latest swc. plugins simply doesn't work, and swc authors working on that. You can follow discussing here vercel/next.js#46989 (comment) and here lingui/swc-plugin#39 and here #6807 (comment)

[timofei-iatsenko]

I saw you mentioned in other discussion that updating to v0.7.40 didn't help, and you tried to implement rmp_serde. So it turned out that update helped?

[kdy1]

The problem was miscompialtion of nightly rustc, not rkyv@0.7.40.
I think it solves the issue, but I can't be sure at the moment.

[timofei-iatsenko]

that's bad because it explodes segmentation of the plugin ecosystem. Right now to support different version of nextjs i need to compile and distribute my plugin with diffrent version of swc_core and rustc. (and it still will not work for example in plain @swc/core because next-swc build with different version of nighly rust)

[kdy1]

So what can I do? There's no solution to this problem at the moment.

[timofei-iatsenko]

Agree, just adding a bit of input. Hope you find a solution. Great work anyway.