Meteor 3.3.x and meteortesting:mocha/lmieulet:meteor-coverage

[harry73]

Hi @ferjep

Currently i use Meteor 3.4-beta-11 (with rspack 1.5.8) and swc-plugin-coverage-instrument 0.0.31 without any pb.

For 3.3.2, i need to check again but do not have much time.

[ferjep]

Thanks you for the responses, once I have some time I’ll try out Meteor 3.4-rc.1 with this project.

I’m currently updating another project with 3.4 but I’m having problems

3.4-rc.1 Release Candidate, Faster Builds, Smaller Bundles and Modern Setups with the Rspack integration

Hello there, I’m trying out 3.4-rc.1. Thanks for all the latest updates to Meteor I have a problem with an app, it seems not to be running fine. Server does not seem to print some logs I have for startup, also it is warning about some imports but these are packages installed, so I can’t really fix the code (is there a way to fix these warnings) And client, when loading via browser, is fully blank, like it has crashed or router was not working => Started proxy. [R…

[nachocodoner]

Just want to say here that you don’t need to add rspack in your project when you upgrade to Meteor 3.4-rc.1. You can focus on test it first with the Meteor bundler as you had with Meteor 3.3.x. Updating to latest Meteor 3.4-rc.1 will ensure swc_core could be latest and have swc-plugin-coverage-instrument@0.0.32 hopefully.

[ferjep]

Ah perfect! That’s good to know for a quicker test.

Thanks!

[harry73]

@nachocodoner

Yes, you’re right.

Meteor 3.3.2 is fixed to use @swc/core 1.12.14 through a custom NPM package.

With the latest Meteor 3.4-rc.1 I bumped the internal Meteor SWC version to 1.15.3, which uses swc_core v48.0.2, likely compatible with swc-plugin-coverage-instrument@0.0.32.

Upgrading to Meteor 3.4-rc.1 won’t force you to use the Rspack integration, so you can update and still use the Meteor bundler alone. Besides this, I want to mention that adopting Rspack for your app code will make your setup depend on Rspack, which updates SWC on its own schedule.

Hi @nachocodoner

I tried Meteor 3.4-rc.1 with Rspack integration and swc-plugin-coverage-instrument@0.0.32 without success. My tests fail with the following error.

It seems Rspack installed 1.6.5 (even 1.6.7) uses swc_core 46.0.3 and not the internal Meteor SWC 1.15.3.

ERROR in ./tests/main.js
    × Module build failed (from builtin:swc-loader):
    ╰─▶   × plugin
          │
          │   x failed to invoke plugin on 'Some("/home/harry/Dev/VueGPX/tests/main.js")'
          │ The version of the SWC Wasm plugin you're using might not be compatible with `builtin:swc-loader`.
          │ The `swc_core` version of the current `rspack_core` is 46.0.3.
          │ Please check the `swc_core` version of SWC Wasm plugin to make sure these versions are within the compatible range.
          │ See this guide as a reference for selecting SWC Wasm plugin versions: https://rspack.rs/errors/swc-plugin-version

[nachocodoner]

I see, the internal Meteor SWC was bumped to 1.15.3 in the last RC, which corresponds to swc_core v48.0.2.

It seems our internal Meteor SWC is now ahead of what Rspack uses, so this mismatch could be the issue. Keeping the internal Meteor SWC at the same or a lower version (swc_core 46.0.3) might solve it. Do you think this is the case?

I’m planning a quick rc.2 to include one fix, and I could add this one as well.

[harry73]

My understanding is the following:

swc-plugin-coverage-instrument@0.0.32 need @sw/core 1.15.0 and above because it needs at least swc_core @47.0.0
But I do not know why it seems it is swc_core verson of Rspack that is taken into account.

In Plugin Compatibilty Rspack 1.6.5/7, swc_core is below @47.0.0 and swc-plugin-coverage-instrument@0.0.32 is not listed

My opinion is that we must wait a Rspack release that will bump the swc_core version.

It is new for me so just guessing