Hello
';\nconst customCSS = 'p { color: red; } ';\nconst customJSExtension = 'jsx';\nconst customCssExtension = 'style.js';\n\n(async () => {\n\tawait rcg(\n\t\tcomponentName,\n\t\tsrcFolderPath,\n\t\tcustomDOM,\n\t\tcustomCSS,\n\t\tcustomJSExtension,\n\t\tcustomCssExtension\n\t);\n})();\n```\n\n### Loading options from a config file\n\nRather than having to specify arguments via the CLI each time, you can load them via a rcg.config.js file, with these contents:\n\n```javascript\nconst path = require('path');\n\nconst config = {\n\t// Put the component folder and file in the components directory\n\tdirectory: path.join(process.cwd(), 'components'),\n\t// Use the jsx filename extension for the component files\n\tjsExtension: 'jsx',\n};\n\nmodule.exports = config;\n```\n\nYou can create an rcg.config.js file by running this command:\n\n```\nnpx rcg init\n```\n\nThis will ask you a few questions (which folder to generate components in, which JS file extension to use, and whether to use Next.js SASS module support) and write the answers to an rcg.config.js file.\n\nTo skip the questions and generate the file with default values (useful in CI or scripts), pass the `--yes` flag:\n\n```\nnpx rcg init --yes\n```\n\nIf an rcg.config.js file already exists, you'll be asked to confirm before it gets overwritten (running with `--yes` will overwrite it without asking).\n\n### Running Tests\n\n```\nnpm t\n```\n\n### License and Credits\n\n© 2025 Anephenix Ltd. RCG is licensed under the MIT License.\n","readmeFilename":"README.md"}