Swc migration

[YASHMAHAKAL]

Notes for Reviewers

This PR fixes #

Migrates from Babel to SWC

Signed commits

• Yes, I signed my commits.

[YASHMAHAKAL]

@leecalcote should i also upgrade mocha version ? please take a look

[saurabhraghuvanshii]

@YASHMAHAKAL two times --extension flag, why?

[YASHMAHAKAL]

@saurabhraghuvanshii instead of the comma-separated values, i just added it twice, it matches mocha's current cli behavior

[kishore08-07]

@YASHMAHAKAL I noticed inconsistent module configurations across files: .swcrc and .swcrc.test are using commonjs, while rollup.config.js is configured for es6.
Could we align these configs or rely on Rollup to handle the module format to avoid potential build inconsistencies?

[kishore08-07]

@YASHMAHAKAL @babel/runtime-corejs3 is still in dependencies. Can we remove this?

[YASHMAHAKAL]

@kishore08-07, i had a reason for this, but i thought on that reason again, and now i think i should be removing it, Thanks.

[kishore08-07]

@YASHMAHAKAL shall we update to modern baselines?

[YASHMAHAKAL]

implemented, this made build even faster.. Thanks !

[YASHMAHAKAL]

@YASHMAHAKAL I noticed inconsistent module configurations across files: .swcrc and .swcrc.test are using commonjs, while rollup.config.js is configured for es6. Could we align these configs or rely on Rollup to handle the module format to avoid potential build inconsistencies?

The different module types are intentional and follow the recommended pattern for Rollup + SWC.
The .swcrc commonjs is used by @swc-node/register in Node.js tests, node requires CommonJS.
Inside the Rollup plugin, we use es6 so rollup can perform static analysis and tree-shaking on es module import/export statements. If we set it to commonjs, SWC would convert imports to require() calls before rollup sees them, which would break rollup's tree shaking entirely.

[kishore08-07]

@YASHMAHAKAL I noticed inconsistent module configurations across files: .swcrc and .swcrc.test are using commonjs, while rollup.config.js is configured for es6. Could we align these configs or rely on Rollup to handle the module format to avoid potential build inconsistencies?

The different module types are intentional and follow the recommended pattern for Rollup + SWC. The .swcrc commonjs is used by @swc-node/register in Node.js tests, node requires CommonJS. Inside the Rollup plugin, we use es6 so rollup can perform static analysis and tree-shaking on es module import/export statements. If we set it to commonjs, SWC would convert imports to require() calls before rollup sees them, which would break rollup's tree shaking entirely.

@YASHMAHAKAL Thanks for clarifying, that makes sense.