Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New release #20

Open
wants to merge 36 commits into
base: master
Choose a base branch
from
Open

New release #20

wants to merge 36 commits into from

Conversation

jauco
Copy link
Owner

@jauco jauco commented Feb 13, 2015

  • 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

jauco added 14 commits January 30, 2015 20:01
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
@jauco jauco changed the title Update eslint New release Feb 24, 2015
… 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
jauco added 2 commits April 20, 2015 22:00
…owser that it supports (chrome) has native source-map support for errors that are logged while the console is already open.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants