Add new config option buildDir, rename styleguideDir
See original GitHub issueIt would be nice being able to specify source directory as well as build directory in configuration. That would make project structure cleaner by separating config files from source files.
I would suggest introducing new option: srcDir with default value src and rename stylguideDir to buildDir with corresponding default build
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Configuration - React Styleguidist
You can change the location of the config file using --config CLI option. ... This config object will be added as the second...
Read more >Configuration | Vue Styleguidist
config.js file in your project's root folder. You can change the location of the config file using --config CLI option. # assetsDir.
Read more >react-styleguidist - npm
Add a styleguide.config.js file into your project's root folder. ... examples file but you can change it with the getExampleFilename option.
Read more >React-styleguardist - static assets? - Stack Overflow
Option 1: Change config and structure ... Then update styleguide.config.js to point to the new folder, in my example it is named assets...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’m experiencing with Vue Cli 3 and styleguideDir = ‘designsystem/dist’, that when I run styleguide:build it also creates a /dist directory on the project root. Problem then is this overwrites the build of the application itself (seems to just be a direct copy of files from VUE Cli /public folder). Any clues as to why this may occur?
I do not believe that it is fixed, would you mind opening another issue here?