New release #20
Open
New release #20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
jauco
commented
Feb 13, 2015
jauco
commented
- Update eslint (breaking changes in eslint pragma's)
- update webpack
- use .eslintrc instead of jester.json eslint config (breaking change)
- use webpack.config instead of jester.json webpack config (breaking change)
- karma can now load polyfills for you
- bugfixes
- No longer overwriting test files with same basename in jester-batch
- No longer running tests from .chunk.js files that webpack sometimes generates unless they're required from an entrypoint
- less precise matcher for finding the test file for a js file
It's used as a constant anyway, this removes code duplication
The output path changes depending on whether we are building a test file or a result file. Testfiles must be placed in the directory that karma is watching. Result files must not be placed in that directory. This change makes the entrypoint name be the path differentiator instead of the output.path. This is needed because I want to use the same webpack config for both the test build and the entrypoint build.
Generate a config that has access to jester's config options so I can help in keeping webpack, karma and eslint integrated. But do allow the user to configure webpack as he or she sees fit.
There was an error in the eslintrc
… the test files. Mostly for loading polyfills
… different paths. Also work around the fact that webpack generates a chunk.js containing the same content as the entrypoint js which would result in karma running the same test twice
…y around handling edge cases (files called .test.js)
…test file that sort of matches
…at the project directory is added to the lookup path
This has the side-effect that jester no longer clears the directory before generating artifacts.
…owser that it supports (chrome) has native source-map support for errors that are logged while the console is already open.
Made createEntryModules work on Windows (escape directory separator)
Use webpack entry points
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.