Feel free to ask questions related to the book content or React here. I'll get to them eventually. Stack Overflow or Reactiflux is likely faster for general questions, though.
Hey all. I've worked my way through the book up until the manifest section where it talks about hashing causing an issue with the vendor bundle when the application code is changed. That isn't happening with my code though - the vendor hash remains the same if I change the application code. Any ideas on why, or what I've missed?
Loving the book by the way, if the author is here :)
maybe something changed in webpack
i'm close to a new release of the book btw, see the
dev branch at https://github.com/survivejs/webpack-book
it's a lot of modernization + preparation for webpack 5
they added what's called
contenthash to webpack but it appears to be buggy in webpack 4 (should be ok in 5)
speaking of react, i wrote https://tailwind-webpack-starter.netlify.app/ . it gives you react style component model without react. overall the solution is extremely light (check the network tab)
here are the changes so far, https://github.com/survivejs/webpack-book/compare/v2.4.9...dev
likely i'll check your repository tomorrow morning as it's getting late
should be good now
i checked your repository and i can confirm what you saw
it's possible this has to do with module indexing/numbering internally and now it's more stable by default than before when it was invalidating them inadvertently
It's always nice to find it's not simply down to me misunderstanding a newish topic! :D
Speaking of which, I do have a couple of questions on some odd behaviour I'm getting implementing multipe pages if you don't mind - but for the time being I'll leave you to enjoy your weekend! Thanks for taking a look, much appreciated!
if you want to compare, i have a multi-page setup at https://github.com/survivejs/tailwind-webpack-starter
it's a bit more complex than in the book
it's doing bundle per page by convention and also a shared bundle for any global dependencies
internally it's typed-html, typescript, tailwind, and sidewind
the next step might be iterating on the components and adding the ones i'll need in the immediate future in addition to implementing incremental compilation for production (avoids lots of work)
i improved the code editor somewhat (it supports jsx way better now), https://tailwind-webpack-starter.netlify.app/design-system/
there are also more components (still missing a couple of the vital ones)
i added an initial version of component code editor to the thing, https://twitter.com/bebraw/status/1294955118232834053
there's a design system themed mini-conf 22nd of September
Adn good morning BTW
i have been using https://github.com/lukejacksonn/oceanwind with great success. it's a bit early days but it's great
it's a super cool vs code plugin for sorting tailwind class names