Error resolving @storybook/icons in v2.1.1

[cflee]

After upgrading to [email protected] which pulls in [email protected], my storybook build is reporting this:

✘ [ERROR] Could not resolve "@storybook/icons"

    node_modules/storybook-i18n/dist/manager.js:4:26:
      4 │ import { GlobeIcon } from '@storybook/icons';
        ╵                           ~~~~~~~~~~~~~~~~~~

  You can mark the path "@storybook/icons" as external to exclude it from the bundle, which will
  remove this error.

This seems to be new usage of this package @storybook/icons in #21 – it was previously using Icons from @storybook/components. Is there some dependency change that needs to be done to include this package?

[stevensacks]

Version 2.1.x is for Storybook 8 (which is currently in Beta).

You can downgrade back to 2.0.x to use with Storybook 7, or you can upgrade your Storybook to the beta 8 release.

[stevensacks]

Storybook 8 has been released.

[davideme]

This make us fail our CI/CD pipeline too, would have been nice to follow semantic versioning. Using version 3.0 for SB8 instead of 2.1

[stevensacks]

@davideme I apologize. You are correct. I will fix this by removing the 2.1 releases and replacing with 3.x.

[stevensacks]

I have removed the 2.1 releases.

• 2.x is Storybook 7
• 3.x is Storybook 8

[anthonyminyungi]

This package's v2.1.1 and v2.1.2 are still downloadable from npm.
The package manager is still detecting and downloading those versions.
Could you unpublish those versions from the registry like releases?

[stevensacks]

Ah sorry. Yes, I’ll unpublish them.

[stevensacks]

npm does not allow me to unpublish, but I have deprecated those versions. That's the best I can do.

I'm sorry for the inconvenience. In the future, I will be sure to bump the major version for new major versions of Storybook.

[anthonyminyungi]

@stevensacks Is there any possibility of adding a new version after 2.1.2 for Storybook 7?

We are using the ^2.0.10 version of storybook-react-i18next and it still gets an error because the versions(2.1.1 and 2.1.2) causing errors (because they depend on the same version of this package) are still installed automatically by the package manager even if they are deprecated on npm.

So I would like to check if there is a possibility that a new version of the package for Storybook 7 after 2.1.2 will be added so that we are okay to use the fixed version 2.0.10 of storybook-react-i18next to resolve the error.

[stevensacks]

Can you pin it to 2.0.10?

[anthonyminyungi]

@stevensacks Yes. If there is no plan for adding the new version in major 2, we'll use 2.0.10 as pinned while we're using Storybook 7.