v1.5.20 exploded. Please fix version to 1.5.7 for now about swc HOT 16 CLOSED

The latest tag is now 1.5.7

from swc.

PLEASE UNPUBLISH @swc/[email protected] FIRST!!!

from swc.

To resolve this, fix the version of "@swc/core": "1.5.7". No caret(^)

"dependencies": {
  "@swc/core": "1.5.7"
}

If @swc/core is not installed, install version 1.5.7:

npm install @swc/[email protected]
# or
yarn add @swc/[email protected]
# or 
pnpm install @swc/[email protected]

from swc.

76b4de1 would fix it, but I'll close this issue after verifying that it works.

from swc.

I'm trying my best. And normally, you don't need overriding because the latest tag of npm is 1.5.7

from swc.

@kdy1 Overriding is still necessary if @swc/core's version is defined as a version range (e.g. ^1.5.7). Then, it doesn't matter which version is tagged with latest. The package manager yarn (v4) will install the latest available stable version that is published (as of now 1.5.20 - which is borked as well). This is an issue at Storybook because @swc/core is a transitive dependency, and we have to publish new versions of our packages so that our users will not run into issues.

// from the `yarn.lock`
"@swc/core@npm:^1.5.7":
  version: 1.5.20
  resolution: "@swc/core@npm:1.5.20"
  ...

from swc.

Finally it's fixed.

from swc.

I'm guessing that is the cause for pnpm/pnpm#6603 (comment) ?

ERR_PNPM_WORKSPACE_PKG_NOT_FOUND  In : "@swc/types@workspace:^" is in the dependencies but no package named "@swc/types" is present in the workspace

Most likely, I'm having the same issue

from swc.

I'm guessing that is the cause for pnpm/pnpm#6603 (comment) ?

ERR_PNPM_WORKSPACE_PKG_NOT_FOUND  In : "@swc/types@workspace:^" is in the dependencies but no package named "@swc/types" is present in the workspace

from swc.

looks like the way publishing worked in swc changed maybe some hooks are no longer running as expected? v1.5.11...main

from swc.

Ran into the same problem, did you use npm directly when publishing

from swc.

@Aarebecca Yeap, exactly. I changed it to use yarn npm publish and triggered a new release

from swc.

@kdy1 any thoughts on using pnpm I've found using it for monorepo management to be a lot easier especially around publishing

from swc.

from swc.

Same here

from swc.

Will this issue be resolved soon ? Or I'll just do update using "resolutions": {"@swc/core":"1.5.7"}

from swc.