/* webpack.config.js */ require('style-loader'); require('css-loader'); var path = require('path'); const projectName = 'rhodecode-components'; let destinationDirectory = path.join(process.cwd(), 'rhodecode', 'public', 'js') if (process.env.RC_STATIC_DIR) { destinationDirectory = process.env.RC_STATIC_DIR; } module.exports = { // Tell Webpack which file kicks off our app. entry: { main: path.resolve(__dirname, 'rhodecode/public/js/src/components/index.js'), }, output: { filename: 'rhodecode-components.js', path: path.resolve(destinationDirectory) }, // Tell Webpack which directories to look in to resolve import statements. // Normally Webpack will look in node_modules by default but since we’re overriding // the property we’ll need to tell it to look there in addition to the // bower_components folder. resolve: { modules: [ path.resolve(__dirname, 'node_modules'), path.resolve(__dirname, 'bower_components') ] }, // These rules tell Webpack how to process different module types. // Remember, *everything* is a module in Webpack. That includes // CSS, and (thanks to our loader) HTML. module: { rules: [ { // If you see a file that ends in .html, send it to these loaders. test: /\.html$/, // This is an example of chained loaders in Webpack. // Chained loaders run last to first. So it will run // polymer-webpack-loader, and hand the output to // babel-loader. This let's us transpile JS in our `