-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load config from NPM package #183
Comments
Hello, I also looking for such option. ect. Looks like the |
Sharing a preset across teams or packages is a great way to reduce complexity. It surprises me that PostCSS forces me to use a
postcss.config.js
file rather than giving me the option to point to a shared package.Passing a package name instead of a simple path is easy to integrate with existing options. An intuitive command line syntax might look like this:
Although, the preferred option would clearly be referencing it in
package.json
:Prettier implements sharing configs quite beautifully with its
package.json
option.To minimize friction for the user, the path string should optimally be resolved in the same way module paths are resolved in Parcel or Webpack.
The text was updated successfully, but these errors were encountered: