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

Upgrade to Jest 22 #438

Closed
jaredpalmer opened this issue Dec 21, 2017 · 5 comments
Closed

Upgrade to Jest 22 #438

jaredpalmer opened this issue Dec 21, 2017 · 5 comments

Comments

@jaredpalmer
Copy link
Owner

  • Upgrade to Jest 22.

  • Also explore new Jest helper for TypeScript

@FabioAntunes
Copy link
Contributor

FabioAntunes commented Jan 15, 2018

shouldn't this be just bumping the version on the package.json?

It's just with React 16, some errors are being swallowed so it would be nice to get Jest 22 facebook/react#11098

@JacopKane
Copy link

#462

@jamesbhobbs
Copy link
Contributor

@jaredpalmer The current version of Jest in the razzle package has these vulnerabilities: https://snyk.io/test/npm/razzle Is there a reason why a simple version bump of jest wouldn't be ok (as fabio suggested)? I've tried bumping to what you have in this repo's base package.json here #648 and tests pass.

@stale
Copy link

stale bot commented Aug 15, 2018

Hola! So here's the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally--seriously--this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal.

@stale stale bot added the stale label Aug 15, 2018
@stale
Copy link

stale bot commented Aug 22, 2018

ProBot automatically closed this due to inactivity. Holler if this is a mistake, and we'll re-open it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants