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.
@bebraw Maybe you can have a look if you are interested main-bundle.js and vendors-bundle.js I don't expect for you to have the time but if you do I would really appreciate it. FYI: I'm renaming the jsonpFunction to "noconflictJsonp". Please let me know, I would gladly compensate you for your time.
@navarrorc got it. see
main-bundle.js and line deferredModules.push([0,"vendors~main"]);. i think the behavior is by design. webpack runtime has been designed to wait for the vendor to appear so the order doesn't matter
i've been working towards a new release of the book
now the question is, should i base it with webpack 4 (stable) or webpack 5 (alpha)? i'm learning towards webpack 4
i'm cleaning up some of the book and also adding new info where it's relevant
it's roughly 300 action points to shift through so likely i'll have to release in pieces
Hey @bebraw, first just wanted to say I appreciate all the work you put into the book, it's been super helpful! I'm currently trying to load mocha tests in the browser as part of a React app and I have it working (thanks to the Testing chapter), however I'd like to be able to filter which tests are displayed based on the state of my app. I'm trying to use the return value form
require.context() to find the module I want to require like this. It works on initial render, e.g. only the first test module is executed, but when I try to require another module the previous test modules are still executed and I get this error:
I tried clearing the previous test modules from the
require cache but that didn't work. Interestingly, if a hot reload is triggered the error goes away and the proper test is displayed. If I was using mocha without webpack I would just use the grep option, but I was hoping to get it working with webpack as I want to take advantage of hot reloading to maintain the state of my app. Any thoughts would be a huge help!
The app is meant to be a series of challenges for building React components, so my idea was to have the test output as part of the app itself to guide development (in true TDD fashion). Since
require.context() allows you to iterate over a set of modules via the keys() method I thought I could use that to only load certain modules based on the state of my app, but after much trial and error I may end up just loading all the tests and querying the DOM to only display one test suite at a time
@okanthony would it be cleaner to run the mocha tests in browser directly? reference: https://stackoverflow.com/a/42858362/228885
maybe it's worth checking what codesandbox is doing. i am missing the big picture a little bit
@okanthony it's likely worth looking into mocha apis. maybe they have something specific for this? just for reference, i wrote a browser oriented testing lib many moons ago (https://github.com/bebraw/bunit.js)
@krandom what's the use case? can you give some context?
then you have more flexibility at least
So, say I have a SVG asset and I want to load it using the
react-svg-loader. But I only want this to the case when directly importing it, i.e import "myLogo.svg" not when the asset is referenced in, say, <img src="myLogo.sg" /> in which case I need the file-loader to work
But this is a bit uggly
I was trying to figure out if using
issuer in a certain way would do it
But it's also probably a dead-end
Can't limit it to, say, where it' s used
One - hacky - solution would have been to be able to do src="!file-loader!..."
but we can't