Major: use swc-loader for TypeScript compilation

[styfle]

This is a major change since swc doesn't perform type checking, only compilation of TS to JS

TODO: remove transpileOnly flag since it is always true now

[styfle]

@guybedford @sokra @kdy1 @huozhi Any thoughts on how to solve this one?

The module.exports = require("shebang-loader") is converted to module.exports = eval("require")("shebang-loader").
But I would expect the contents of the shebang-loader package instead.
Fixed that part in c68542c.

Now the JS integration tests pass but the TS ones fail with the following:

    Module build failed (from ./dist/ncc/loaders/swc-loader.js):
    Error: Can not load bindings
    Installed packages: [core-darwin-x64]

[kdy1]

It seems like node failed to resolve @swc/core-darwin-x64 from ./dist/ncc/loaders/swc-loader.js.

But I'm not sure about the reason, as I found yarn install in the CI script.

[styfle]

@kdy1 The paths and baseUrl tests are failing with:

panicked at 'failed to get current directory: Error { kind: Unsupported, message: "operation not supported on this platform" }', /home/runner/work/swc/swc/ecmascript/transforms/module/src/path.rs:81:56

Stack:

Error: 
    at u.exports.__wbg_new_59cb74e423758ede (dist/ncc/loaders/swc-loader.js.cache.js:1:2692)
    at null.<anonymous> (wasm://wasm/04480186:0:15193164)
    at null.<anonymous> (wasm://wasm/04480186:0:16752724)
    at null.<anonymous> (wasm://wasm/04480186:0:16566604)
    at null.<anonymous> (wasm://wasm/04480186:0:16677644)
    at null.<anonymous> (wasm://wasm/04480186:0:16749249)
    at null.<anonymous> (wasm://wasm/04480186:0:16736138)
    at null.<anonymous> (wasm://wasm/04480186:0:16687572)
    at null.<anonymous> (wasm://wasm/04480186:0:5322716)
    at null.<anonymous> (wasm://wasm/04480186:0:15233495)

[styfle]

@kdy1 The new @swc/wasm no longer panics, but it still fails with very strange behavior.

Input:

https://github.com/vercel/ncc/blob/main/test/unit/tsconfig-paths/input.ts

import module from "@module";

console.log(module);

Output:

/******/ 	var __webpack_modules__ = ({

/***/ 105:
/***/ ((module) => {

module.exports = eval("require")("../../../../../../../../.././module");


/***/ })

/******/ 	});

Runtime result:

Error: Cannot find module '../../../../../../../../.././module'

[harisvsulaiman]

Now that swc is extensively used at vercel, swc support in ncc would be hugely beneficial.