survivejs/webpack

Feel free to ask questions related to the book content or webpack here. I'll get to them eventually. Stack Overflow or Reactiflux is likely faster for general questions, though.

Juho Vepsäläinen

@bebraw

and that's with all features

Stefan Frede

@stefanfrede

I had a look at https://github.com/ryangjchandler/spruce for state management with Alpine.js.

Juho Vepsäläinen

@bebraw

i checked webpack-cli - it's literally using webpack's node api and capturing stats from there

interesting, let me check that one out :)

it's that JS part that's instant turn off for me

i wanted something that can live in HTML. i still use globals for exposing things like highlighting but try to keep that to minimum

that said, spruce likely integrates better with an existing system

it looks like the best bet would be to implement --json to webpack-nano. i'll ask andrew about that

Stefan Frede

@stefanfrede

That woul be cool!

Juho Vepsäläinen

@bebraw

it doesn't add much weight to it

maybe i just get it done now :)

Stefan Frede

@stefanfrede

Juho Vepsäläinen

@bebraw

here we go, shellscape/webpack-nano#18

Stefan Frede

@stefanfrede

Awesome!

Juho Vepsäläinen

@bebraw

andrew has been busy lately but i hope he can get to it soon enough

book driven development :)

that's why i wrote webpack-merge as well - i needed it for the book

Stefan Frede

@stefanfrede

Your book was and is for me the best ressource for a sane webpack config!!!

Juho Vepsäläinen

@bebraw

the approach is still valid - i have a client case where i ported something quite complex into a config package they can share across their projects

these days the trend seems to be that frameworks like next manage webpack config for you

and i guess the next generation will do something a bit different on browser level even. deno is cool in that regard

Stefan Frede

@stefanfrede

It seems that the cool new tools are "dealing" with the complexity of webpack for you, but most often than not you have to tweak someting and then it is good to have at least a bit of an understanding aboout webpack.

Juho Vepsäläinen

@bebraw

definitely, that's when understanding the tool pays off

i know rollup is getting more popular and starting from vue 3, they go with it by default through vite (opinionated rollup)

it's still quite small compared to webpack in terms of downloads, though

Stefan Frede

@stefanfrede

My plan at the moment is to start learning Vue now that v3 is out.

Juho Vepsäläinen

@bebraw

it's interesting to see where vue will be within a year

i feel react has been stagnating a bit as people are waiting for suspense

react 17 won't bring any new features either

at the same time that's a sign of stability

Stefan Frede

@stefanfrede

I start to get the feeling that my portfolio needs one of the big names in it and Vue seems to stick quite closely to the native web components stuff.

at the same time that's a sign of stability

That is true!

Juho Vepsäläinen

@bebraw

i got a quick review from andrew at shellscape/webpack-nano#18 . it's possible the feature lands soon :)

Stefan Frede

@stefanfrede

👍

Juho Vepsäläinen

@bebraw

it was merged - now just waiting for a release

Juho Vepsäläinen

@bebraw

i sketched out a more powerful way to handle arbitrary merges at webpack-merge - survivejs/webpack-merge#150

Stefan Frede

@stefanfrede

it was merged - now just waiting for a release

🎉

Juho Vepsäläinen

@bebraw

i added a powerful new feature to webpack-merge https://twitter.com/bebraw/status/1313774533292240897

now you can merge complex cases declaratively

Juho Vepsäläinen

@bebraw

@stefanfrede it's out https://www.npmjs.com/package/webpack-nano

Stefan Frede

@stefanfrede

@bebraw Thank you!

quanganhtran

@quanganhtran

Good day! If I have a single static bundle that I want to serve with different configs (and/or assets) depending on backend environment, how should I approach this? Preferably without html templating.

right now I'm building two different bundles based on env

but I want to use just one. the env-specific part probably can be extracted out and served remotely or something...

Stefan Frede

@stefanfrede

@quanganhtran Something like this should work:

const commonConfig = { ... };

const productionConfig = { ... };

const developmentConfig = { ... };

module.exports = env => {
  switch(env) {
    case 'development':
      return merge(commonConfig, developmentConfig);
    case 'production':
      return merge(commonConfig, productionConfig);
    default:
      throw new Error('No matching configuration was found!');
  }
}

Juho Vepsäläinen

@bebraw

yup, that's a good pattern

i've found switch/case to be nice for the purpose

Martin Oppitz

@martinoppitz

Hello, I checked webpack v5 with aurelia an svelte. It does not work.

Need we a Ticket?

Juho Vepsäläinen

@bebraw

@martinoppitz is this related to the book content? if it's something beyond the book, like it's best to open a report at https://github.com/webpack/webpack/issues

Where communities thrive

People

Repo info

Activity