Default / base Webpack config
See original GitHub issueSimilar to what Storybook has but more explicit and not all-or-nothing:
const path = require('path');
const loaders = require('react-styleguidist/loaders');
module.exports = {
title: 'React Style Guide Example',
components: 'lib/components/**/[A-Z]*.js',
webpackConfig: {
loaders: [
loaders.babel,
loaders.css,
{
// Some custom loader
},
],
},
};
CLI tool (#208) should generate config similar to create-react-app by default.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Configuration - webpack
webpack applies configuration defaults after plugins defaults are applied. Webpack has a huge set of options which might be overwhelming to you, ...
Read more >An Introduction to Webpack Configs - Mastering JS
Webpack configs allow you to configure and extend Webpack's basic functionality. A Webpack config is a JavaScript object that configures one ...
Read more >Default webpack configuration - Stack Overflow
Out of the box, webpack won't require you to use a configuration file. However, it will assume the entry point of your project...
Read more >How to configure Webpack 4 or 5 from scratch for a basic ...
With that basic setup, you can run $ npm run build command. Webpack will look up our entry file, resolve all import module...
Read more >webpack.config.base.js - gists · GitHub
module.exports.defaults = defaults;. module.exports.extend = function merge(config) {. return _.extend({}, defaults, config);. } ...
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
Let’s me develop my idea: people wants stuff that works out of the box, no config (or really minimal stuff like a folder path) should be enough for your project (see CRA or next.js). I think I did this mistake with Phenomic: I want everything to be customisable so people needs to configure before using it: generally a bad idea, people want to try with minimal effort before actually using a tool. Also supporting tools without any user effort should be made when doable. For example now Phenomic support Glamor or Aphrodite out of the box, nothing to do from your side if we can do it. I know it requires some work but it will make your project more easy to try. I honestly tried some others, but never happy. styleguidist is slow and have other problems, but it works! Having setup more easy will bring more users, so more contributors on the long run 😃
@aaronjensen I’m afraid it’s much more complicated than you think and more complicated than what @MoOx and @okonet are suggesting. It could make Styleguidist more flexible but won’t make initial setup much simpler.