feat(misc): update @swc/helpers version to match @swc/core

[jaysoo]

@swc/core has a peer dep on @swc/helpers, but ours is out of date so it's leading to an issue like the following:

 npm ERR! ERESOLVE could not resolve
    npm ERR! 
    npm ERR! While resolving: @swc/[email protected]
    npm ERR! Found: @swc/[email protected]
    npm ERR! node_modules/@swc/helpers
    npm ERR!   dev @swc/helpers@"~0.4.11" from the root project
    npm ERR!   @swc/helpers@"^0.4.11" from @nx/[email protected]
    npm ERR!   node_modules/@nx/vite
    npm ERR!     @nx/vite@"16.0.0" from @nrwl/[email protected]
    npm ERR!     node_modules/@nrwl/vite
    npm ERR!       dev @nrwl/vite@"^16.0.0" from the root project
    npm ERR!       1 more (@nx/vite)
    npm ERR!   1 more (next)
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peerOptional @swc/helpers@"^0.5.0" from @swc/[email protected]
    npm ERR! node_modules/@swc/core
    npm ERR!   dev @swc/core@"^1.2.173" from the root project
    npm ERR!   peerOptional @swc/core@"^1.2.173" from [email protected]
    npm ERR!   node_modules/nx
    npm ERR!     dev nx@"16.0.0" from the root project
    npm ERR!     3 more (@nrwl/tao, @nx/devkit, @nx/workspace)
    npm ERR!   3 more (ts-node, @swc/jest, swc-loader)
    npm ERR! 
    npm ERR! Conflicting peer dependency: @swc/[email protected]
    npm ERR! node_modules/@swc/helpers
    npm ERR!   peerOptional @swc/helpers@"^0.5.0" from @swc/[email protected]
    npm ERR!   node_modules/@swc/core
    npm ERR!     dev @swc/core@"^1.2.173" from the root project
    npm ERR!     peerOptional @swc/core@"^1.2.173" from [email protected]
    npm ERR!     node_modules/nx
    npm ERR!       dev nx@"16.0.0" from the root project
    npm ERR!       3 more (@nrwl/tao, @nx/devkit, @nx/workspace)
    npm ERR!     3 more (ts-node, @swc/jest, swc-loader)
    npm ERR! 
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 17, 2023 6:46pm

[AgentEnder]

I was looking at this at the end of Friday- thanks for taking care of it.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit b59321b. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 8 targets

• nx affected -t e2e-macos --parallel=1 --exclude=e2e-detox
• nx affected --target=e2e --base=81f5603998f58336e58e5fd07e535284974d5f9e --head=b59321bc12cb68ef42c094be6625653f1831167d --parallel=1
• nx run-many -t check-imports check-commit check-lock-files depcheck --parallel=1 --no-dte
• nx affected --target=lint --base=81f5603998f58336e58e5fd07e535284974d5f9e --head=b59321bc12cb68ef42c094be6625653f1831167d --parallel=3
• nx affected --target=build --base=81f5603998f58336e58e5fd07e535284974d5f9e --head=b59321bc12cb68ef42c094be6625653f1831167d --parallel=3
• nx affected --target=test --base=81f5603998f58336e58e5fd07e535284974d5f9e --head=b59321bc12cb68ef42c094be6625653f1831167d --parallel=1
• nx-cloud record -- nx format:check --base=81f5603998f58336e58e5fd07e535284974d5f9e --head=b59321bc12cb68ef42c094be6625653f1831167d
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[barbados-clemens]

does webpack/js also need to bump versions?

https://github.com/nrwl/nx/blob/master/packages/js/src/utils/versions.ts#L8
https://github.com/nrwl/nx/blob/master/packages/webpack/src/utils/versions.ts#L4

[jaysoo]

I'll push a PR for the version.ts files too.

The main problem was that we used ~ for core and ^ for helpers, which I think was my fault. According to semver ~ for pre 1.0.0 releases behave the same as ^ for 1.0.0 releases, so there's no reason to use different ranges.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.