Config Options
Our configurable options simplify CLI configuration, making it easier and more efficient.
cssPreprocessorTakes
stringvalue to specify the preprocessor for the component to be generated which includescss,pcss,scss, etc.Note:
cssis the default value forcssPreprocessor.usesTypeScriptTakes
booleanvalue to specify whether to useTypeScriptas template for the component or not.Note:
trueis the default value forusesTypeScript.scopeStyleTakes
booleanvalue to specify whether to use scoped css modules for the component or not.Note:
falseis the default value forscopeStyle.addStoryTakes
booleanvalue to specify whether to addstorybookstories for the component or not.Note:
falseis the default value foraddStory.addIndexTakes
booleanvalue to specify whether to add index file for the component or not.Note:
falseis the default value foraddIndex.addTestTakes
booleanvalue to specify whether to add test file for the component or not.Note:
falseis the default value foraddTest.flatTakes
booleanvalue to specify whether to generate component without parent folder or not.Note:
falseis the default value forflat.pathTakes
stringvalue to specify the path to where the component should be generated.Note:
./is the default value forpath.cautionOnly relative path is accepted by the
pathoption. So using absolute path may lead to an unexpected error.customTemplateTakes an object structure with valid properties like
component,style,storyandtestthat allows user to provide their own custom templates for the component they want to generate more.
Override the options for generating a certain component
You can override the options in arclix.config.json, if you want some options needed only for generating a certain component by adding the flags.
For example: If you want Contact to go in pages folder but you have configured path in config file to ./src/components then you can use --path or -p flag to override the path temporarily only for that component.
npx arclix g c Contact --path="./src/pages"