![]() Simply add the name of the built-in plugin to the list in your file where it should run, like this: You have complete control over the final order of ALL plugins, both custom and built-in. Plugin OrderĬodeKit will run your custom plugins exactly as you configure them, in the exact order you specify.ĬodeKit has several PostCSS plugins built-in:ĬodeKit runs your custom plugins before all of the plugins in the list above. If there are no options for a particular plugin, pass an empty object. Make "plugins" an object with key-value pairs of plugin names matched with an object of options to use when running that plugin: // If you need to pass options to plugins, restructure your config file. (It MUST be named exactly that and it MUST be in the root project folder.)Īdd the custom plugin you want to run to the list in the config file, like this: // Īs long as the plugin is installed in your project, you don't need to supply a path. ![]() You can do that in CodeKit's UI as well.Ĭreate a file named in your project's root folder. This places the plugin and its dependencies in the node_modules folder within your project so that CodeKit can run it.įor projects that already have a package.json file, you might choose to simply install from that file. The most popular ones are built into CodeKit, but you can run any plugin with any configuration you want.įirst, open the Packages area, then search for and install the plugin you want:
0 Comments
Leave a Reply. |