You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chalk is out of date. If the main project needs chalk, and installs the latest version (and why wouldn't it) it will break JSS and cause #1980.
Updating chalk is a inoffensive task, and has little to no consquences in terms of code changes.
There's no real reason to stick with an old version of a dependency, especially seeing how it forces the main project to get stuck on that old version as well. This is why it's important that packages people might use, update their depedencies. Not just chalk, but in this case it's causing a real-world issue.
To Reproduce
Install chalk 5.3.0 in any Next.js based JSS project and see how the build explodes.
Expected Behavior
Build doesn't explode?
Possible Fix
Update chalk.
Provide environment information
Sitecore Version: 10.4
JSS Version: 22.2.1
Browser Name and version: Firefox latest
Operating System and version (desktop or mobile): desktop, Windows 10
Link to your project (if available): N/A
The text was updated successfully, but these errors were encountered:
Describe the Bug
Chalk is out of date. If the main project needs chalk, and installs the latest version (and why wouldn't it) it will break JSS and cause #1980.
Updating chalk is a inoffensive task, and has little to no consquences in terms of code changes.
There's no real reason to stick with an old version of a dependency, especially seeing how it forces the main project to get stuck on that old version as well. This is why it's important that packages people might use, update their depedencies. Not just chalk, but in this case it's causing a real-world issue.
To Reproduce
Install chalk 5.3.0 in any Next.js based JSS project and see how the build explodes.
Expected Behavior
Build doesn't explode?
Possible Fix
Update chalk.
Provide environment information
The text was updated successfully, but these errors were encountered: