Alexander Akait

@baalexander @laggingreflex i can maintain, also found bug `browser-sync` use ```js portScanner.findAPortNotInUse(port, max, { host: "localhost", timeout: 10000000000 }, cb); ``` but `findAPortWithStatus` function don't accept arguments from `object` :disappointed:...

@laggingreflex no bug in browsersync issues :disappointed: i find this bug accidentally, but i can link link to lines with issue

@laggingreflex link to problem lines https://github.com/BrowserSync/browser-sync/blob/3aced708d47f032905721d01dd435d809d8feb33/lib/utils.js#L126

swc and webpack are planned smoothly integration so if you want to avoid big changes/refactor/unpredictable bugs, prefer to use swc (part of integration - https://github.com/swc-project/swc/tree/main/crates/swc_webpack_ast), also swc has better perf...

Please read: > also swc has better perf in some cases, but they both are fast. I am more about - `swc` provides more things out of box, so if...

Next.js starts to migrate on swc (rust), and replace webpack more and more, so you should not afraid it, as I written above it will be smoothly migration

Maybe useful https://webpack.js.org/configuration/experiments/#experimentslazycompilation

@slorber I see, currenty my reccomendation is trying to switch from babel to swc (and swc minifier) too, it should help very well, also swc is more mature now

Using `node`: **test.mjs** ```js import cjs from './foo.cjs'; import mjs from './foo.mjs'; console.log(cjs); console.log(mjs); ``` **foo.cjs** ```js // For: // module.exports = { default: 'cjs' }; // // output node...

CommonJS doesn't have `default` export