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
The package is @csstools/csstools-cli and this is a global CLI for all of our plugins. With the process of moving to this mono-repo we added the CLI to all of the packages but it was kept separately. This means that it was "slightly" increasing the size of the package for something that was going to be rarely used since we haven't done any job on explaining how that works.
Well, we've decided to start reducing the size of our packages to keep a leaner ecosystem and this is one of the first steps we're taking in this direction.
As it's hinted in the README of the project, we recommend using the CSSTools CLI as a prototyping and debugging tool. ⚠️ If you are building/customizing a toolchain it is best not to use the CLI.
The CLI is useful for a quick & dirty solution, to debug problems isolating them from build tools (such as Webpack or Parcel) but not as a production pipeline recommendation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We've just released a new package 🎉!
The package is
@csstools/csstools-cli
and this is a global CLI for all of our plugins. With the process of moving to this mono-repo we added the CLI to all of the packages but it was kept separately. This means that it was "slightly" increasing the size of the package for something that was going to be rarely used since we haven't done any job on explaining how that works.Well, we've decided to start reducing the size of our packages to keep a leaner ecosystem and this is one of the first steps we're taking in this direction.
As it's hinted in the README of the project, we recommend using the CSSTools CLI as a prototyping and debugging tool.⚠️ If you are building/customizing a toolchain it is best not to use the CLI.
The CLI is useful for a quick & dirty solution, to debug problems isolating them from build tools (such as Webpack or Parcel) but not as a production pipeline recommendation.
We'd love to know if you have any feedback!
Beta Was this translation helpful? Give feedback.
All reactions