fix(rspack_loader_swc): enable SWC plugins

[dm33tri]

Summary

Fixes #5763

I've locked rkyv to version which is used in swc and wrapped tuple in a struct as it wouldn't deserialize with an older rkyv version

Require Documentation?

• No

[CLAassistant]

All committers have signed the CLA.

[dm33tri]

You may use this as a base or maybe I will add some test cases later

Also I had some runtime problems running pre-commit linters and didn't bother but will look into it

[h-a-n-a]

Would you please add a case? ;-)

[dm33tri]

Would you please add a case? ;-)

I have added a test case

[dm33tri]

I didn't notice stats snapshot failing locally because my $HOME has . in it and it was replacing it with X and all stats snapshot tests failed. I've fixed this regexp:

// CHANGE: The time unit display in Rspack is second
.replace(/[.0-9]+(\s?s)/g, "X$1");

Removed old test, and updated snapshots

On my machine Diagnostics test set is still failing because it expects .js in stack traces but mine shows .ts

As for timeout of my test I don't know, will rerun fix it?

[dm33tri]

I guess I'll have to spin up a Linux VM or something, because on M1 it passes without any timeouts 😅 To check that it doesn't actually hang

And for CSS - is it just flaky, or did I actually break something?

[h-a-n-a]

I guess I'll have to spin up a Linux VM or something, because on M1 it passes without any timeouts 😅 To check that it doesn't actually hang

And for CSS - is it just flaky, or did I actually break something?

Yes, css test seems flaky and not being fixed. No worries. We will help you out!

Would you please take a look at your earliest convenience? @JSerFeng

[dm33tri]

Issue with the test looks similar to this swc-project/plugins#32 (comment)

[JSerFeng]

the error _require(vm) called after all tests from css urls have completed

I guess the fix could be changing the tests/configCases/css/urls/index.js
to this:

const fs = require("fs");
const path = require("path");

it("css urls should works", async () => {
	await import("./urls.css");
	const css = await fs.promises.readFile(
		path.resolve(__dirname, "bundle.css"),
		"utf-8"
	);
	expect(css).toMatchSnapshot();
});

[JSerFeng]

Also curious how large the @rspack/core package size increases to

[dm33tri]

Also curious how large the @rspack/core package size increases to

rspack.darwin-arm64.node in release mode is up to 45mb from 33mb

I guess the fix could be changing the tests/configCases/css/urls/index.js

I'm able to reproduce this error on different CSS test cases (with require(..) or import(..)) after cleaning up everything (so no caches). Will try few more times to see if it's my changes or not

[JSerFeng]

I'm able to reproduce this error on different CSS test cases (with require(..) or import(..)) after cleaning up everything (so no caches). Will try few more times to see if it's my changes or not

If you have any trouble fixing that, feel free to tell us

[dm33tri]

I see that _require(vm) called after all tests is not from my code and it can flak in any test.

But I can't reproduce build hanging on mac/linux. Can I try to increase timeout for ConfigTestCases.template.js to 30s? Perhaps wasm runtime is just too slow in action runnner

● ConfigTestCases › builtin-swc-loader › swc-plugin › swc-plugin should compile
  thrown: "Exceeded timeout of 10000 ms for a test while waiting for `done()` to be called.

[dm33tri]

Seems like it helped

Would you approve please?

[xc2]

!canary

[github-actions]

0.5.5-canary-9e431a9-20240305043500

[h-a-n-a]

Thank you!