Track and compile tests in webpack #1209
Conversation
This will not process them for now...
This result will not be used for serving the pages but will be used for tracking lint/type errors in those files
rricard
force-pushed
the
tests-in-webpack
branch
from
a27df8d
to
e0d373b
Compare
|
Thanks for looking into this. However most often people will write tests while in |
|
@gaearon I completely agree with that, but at the moment I don't really know how we could integrate this with jest correctly, I have to admit I lack knowledge to extend it. For now, I would say this is a seamless temporary solution to the problem, that is indeed not perfect but will at least do two things:
I'll just take a look at jest to see how we can extend it with eslint (maybe during the transform?) but I think both solutions are complementary: we may want to see those errors in every place and consistently. |
|
@cpojer Do you have any thoughts on integrating lint output in Jest? Is this something you'd take contributions for? For example transforms could get an API to emit custom messages. |
|
@gaearon what do you think about having the warnings both in webpack and jest? |
|
My only concern with doing it in Webpack is it will slow down the dev server because it needs to track more files. |
|
@gaearon well, that's indeed one of my concerns too. If we can get jest to show those errors I'll need to think about the output we want for the flow checking (so it's consistent: not project-wide but only on the concerned files, in both places: tests & server) |
|
I don't think this fits into Jest tbh. Maybe you can convince me. The watch mode needs to be refactored and adding some more information and running a script for more info I'm not completely opposed to if you also do the refactor (basically split the watch feature out of https://github.com/facebook/jest/blob/master/packages/jest-cli/src/jest.js into a separate package). |
|
To sum up the choice is here: Solution 1Webpack and jest shows consistently the same errors for the whole project. Potential con: slower webpack builds Solution 2Webpack will only show errors related to its own bundle. Jest will only show errors related to the files it saw. Potential con: silenced flow errors not seen from one point of view or the other (for instance a mistake in a part of the bundle could trigger an error in the test, we won't see it unless running the tests ...) |
|
@cpojer I could take a look if you are open to it. The idea is just to add some error reporting features into the transform process. We don't need more, from there CRA would handle running eslint/flow. |
|
Honestly, I don't think it will be a good idea to slow down test runs through the use of external tools. I'm worried Jest will be blamed for it. |
|
I mean, that's not the best solution from a DX perspective but I agree that slowing down either one of jest or webpack could be bad... Well, if I had to choose, I would prefer to penalise webpack... |
|
@gaearon I'll try to think about it tonight. Maybe I'll have some other solution tomorrow! |
|
I don't think we'll be moving forward with this. Thanks for taking a look! |
Should fix #1169.
Why would I do that?
Right now CRA checks lint (and soon flow) errors through a webpack compilation process (for example, eslint checks are based on a loader). The issue with this is, this will not check non-imported files in the main app such as tests.
How does this PR solves the problem?
This PR adds files matching a certain "glob" pattern (representing the tests) to the list of watched webpack files as well as triggering an independent child compilation (like html-webpack-plugin does) for those files that will open and process the contents of the files through the available loaders (including eslint) to output them in a tmp dir.
Shouldn't we add this to the
testscript?Doing so would require to add a new way to run eslint on top of the jest watcher. I don't even know if that's possible, however webpack plugins are perfect for this kind of thing!