refactor: Merge @swc/cli into the monorepo

[kdy1]

We also migrate to lerna from turbo because @swc/cli depend on an old version of @swc/cli, which is cyclic and not supported by turbo.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26d98ab

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@mole-inc/[email protected]	environment, filesystem, network, shell	+98	6.66 MB	aaharu
npm/@swc/[email protected]	filesystem Transitive: environment, network, shell	+29	1.55 MB	kdy1
npm/@swc/[email protected]	Transitive: environment, filesystem	+1	484 kB	kdy1
npm/@types/[email protected]	Transitive: environment, filesystem, unsafe	+41	5.62 MB	types
npm/@types/[email protected]	None	+1	4.05 MB	types
npm/@types/[email protected]	None	0	23.5 kB	types
npm/[email protected]	environment, filesystem	+13	357 kB	paulmillr
npm/[email protected]	filesystem, shell	0	144 kB	abetomo
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+250	25.4 MB	simenb
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+523	97.2 MB	jameshenry
npm/[email protected]	environment	+2	452 kB	isaacs
npm/[email protected]	environment	+3	56.1 kB	jinder
npm/[email protected]	unsafe	0	253 kB	metcoder95
npm/[email protected]	environment, filesystem, unsafe Transitive: eval, network, shell	+256	86.6 MB	kul
npm/[email protected]	None	0	60.7 MB	typescript-bot

🚮 Removed packages: npm/@swc/[email protected], npm/@swc/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/@webassemblyjs/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Native code	npm/[email protected]	Location: Package overview	orphan: npm/[email protected]

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]