webpack/webpack

For questions please post on Stack Overflow and use the 'webpack' tag (http://stackoverflow.com/tags/webpack).

Chris

@ipatch

ohh wow my webpack is hashing my classnames

sdyalor

@sdyalor

I'm new in webpack

Hope i could help you in a couple of years

but there is a property in configuration file

Răzvan Idomir

@tsuby

Hi there, is there a way to simulate '[contenthash]' in webpack 3? I need it to basically have a library exposed with a static file name (where the '[contenthash]' would function as a lib version)

For just one file, for the others I still need to use '[hash]'

Peter Müller

@Munter

It's just a string, you can put anything in there. For example libname.${require('./package.json').version}.js

Erwann Mest

@kud

hey

I've got a weird thing in the shell

 Entrypoint undefined = index.html

My code

    entry: ["react-hot-loader/patch", `${SRC_DIR}/index.js`],

It doesn't break anything, my webpack works like a charm, but why I've got this undefined?

cf https://github.com/gaearon/react-hot-loader#getting-started

Răzvan Idomir

@tsuby

@Munter Using [contenthash] would've also been a mechanism to automatically update the "version" number whenever necessary without additional hassle. Thank you for your suggestion, I'll use it :)

ronaklalwaniii

@ronaklalwaniii

Any good tutorial out there to learn webpack? I am a newbie

Diego Gullo

@bizmate

@ronaklalwaniii maybe try https://www.freecodecamp.org/news/tag/webpack/

ronaklalwaniii

@ronaklalwaniii

Thanks, @bizmate i'll check it out.

Peter Müller

@Munter

@tsuby So you just want all files to be content addressable? I highly recommend upgrading your webpack version to opt into those new things

Asim KT

@asimqt

Hi, Can I run my webpack configuration sequentially?.

module.exports = [
  {
    ...webpackConfig,
    ...resolveConfig,
    ...{
      entry: customEntry,
      plugins: enhancedPlugin,
      output: customOutput
    },
    externals
  },
  {
    ...webpackConfig,
    ...resolveConfig,
    ...{
      entry: customEntry,
      plugins: enhancedPlugin,
      module: { ...webpackModule, ...{ rules: enhancedRules } }
    }
  }
];

I actually want one normal bundling for all files and one special library bundling for one specific file. Now things are working in my favor. (It's not perfect) But I want the order to be specified.

Asim KT

@asimqt

Anyone? :)

John Marinelli

@johnmarinelli

@asimqt here is the entrypoint for Multi-config webpack: https://github.com/webpack/webpack/blob/master/lib/webpack.js#L35

it looks like order should be whatever you have in module.exports

Asim KT

@asimqt

mm.. I tried that. In my local system, the order is fine and it's building in different order. Is there a chance that the compiler.run(callback) code will run it in parellel?

@johnmarinelli

Thanks.

John Marinelli

@johnmarinelli

@asimqt i'm not sure because I didn't dig too deep in the code

i think it does though. we use a multi config, but it's an Object, not an Array. the order is the same each time and is alphabetical

Peteris Erins

@Pet3ris

I'm using css-loader to import CSS files while also doing css-in-js using bs-css after the css-loader import has been loaded.

The problem - it seems like the css order between the two files is not deterministic. Sometimes one loads ahead, other times it's the other. Are there any ways to control where styles will be loaded onto the page?

M Xu

@mx2323

hey everyone

ive spent the last few days trying to get my CRA app ported to electron :(

between webpack, babel and eslint issues im really confused.

i think i am close… but im hitting this issue

webpack/webpack#7953

im trying to get webpack to use the non-browser version of superagent in my electron app

but like this issue says using target:’electron-renderer’ causes webpack to pick up the browser version

deAtog

@deAtog

@mx2323 you can change resolve.mainFields so that it will only pick up the main entry from a package's package.json file. This may or may not fix your issue though.

M Xu

@mx2323

Yeah im trying that now (tried it already but it caused all kinds of weird issues)

deAtog

@deAtog

@mx2323 the other option is to provide the absolute path to the file from the node package that you want to import instead of relying on the default resolve behavior

M Xu

@mx2323

the libraries that i am using are relying on the browser field in package.json to package differently… not sure how i would provide an ‘absolute path’

so i tried setting mainFields.. and then i get weird stuff like this -

maybe i need to still specify the target:’electron-renderer’ even when im setting mainFields in webpack.config.js…

brb going to try that

deAtog

@deAtog

@mx2323 you should be able to do: import ... from 'package/path;

M Xu

@mx2323

well… setting target:’electron-renderer’ at least gets me back to a working page

Where communities thrive

People

Repo info

Activity