We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I would like to see more examples of authoring Master CSS plugins/packages.
Suppose you want to create a reusable configuration and publish it to NPM.
{ "name": "aron.css", "main": "master.css.js", "peerDependencies": { "@master/css": "*" } }
/** @type {import('@master/css').Config} */ module.exports = { colors: {}, ... }
That's it. Now publish your package.
config.extends
Install the package just released:
npm i aron.css
Extend it in your current project's configuration file master.css.js:
master.css.js
/** @type {import('@master/css').Config} */ module.exports = { extends: [ require('aron.css') ], ... }
http://beta.css.master.co/docs/configuration/authoring
The text was updated successfully, but these errors were encountered:
1aron
No branches or pull requests
What is the improvement or update you wish to see?
I would like to see more examples of authoring Master CSS plugins/packages.
Is there any context that might help us understand?
Authoring your config package
Suppose you want to create a reusable configuration and publish it to NPM.
./package.json
./master.css.js
That's it. Now publish your package.
Extend your remote config
config.extends
multiple configurations #180Install the package just released:
Extend it in your current project's configuration file
master.css.js
:Does the docs page already exist? Please link to it.
http://beta.css.master.co/docs/configuration/authoring
The text was updated successfully, but these errors were encountered: