Yarn Berry Support
See original GitHub issueThe Chromatic CLI seems to have issues running in a Yarn v2 project. Whenever we run yarn chromatic
we get this error:
UnhandledPromiseRejectionWarning: TypeError: loggly.createClient is not a function
Wondering if this is a known issue with Yarn 2 or something else.
┆Issue is synchronized with this Asana task by Unito
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:27 (16 by maintainers)
Top Results From Across the Web
yarnpkg/berry: Active development trunk for Yarn - GitHub
Yarn supports Node by default but isn't limited to it - plugins can add support for other languages; Yarn supports workspaces natively, and...
Read more >Plug'n'Play | Yarn - Package Manager
Native support; Support via plugins; Incompatible ... Many common frontend tools now support Plug'n'Play natively! ... Flow, Follow yarnpkg/berry#634.
Read more >Support for Yarn 3 - Depfu Blog
We've been dancing around supporting Yarn 2 aka Yarn Berry for a while now because adoption seemed not to be there.
Read more >Yarn Berry: a next generation package manager - YouTube
The recently released Yarn Berry (aka Yarn 2) brings a host of great new features for JavaScript developers. The slick new CLI, ...
Read more >Using the new yarn release (2.0.0 / berry) - Support
tl;dr: remove the YARN_VERSION env config from netlify.toml , check in the contents of .yarn/releases after installing yarn@berry and running yarn in your ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am also getting the following error;
We run this in CircleCI. In the meantime, we’ve got the following step in the job that switches to using the
node-modules
linker for pnp, which allows the job to run successfully:I’m trying to reproduce this.
I made a new storybook repoduction with pnp enabled. https://github.com/ndelangen/storybook-pnp-repro
I immediately ran into a problem getting storybook to run. I applied a hot hack to my .pnp.cjs file and got it to run. https://discord.com/channels/486522875931656193/490070912448724992/875332132535410688
Next I installed chromatic, and my .pnp.cjs file got overwritten, breaking storybook again. I applied my fix again, and got storybook to run again.
Now I try and run the chromatic command, but this fails. Seems yarn pnp and the esm-package are fighting and neither wins.