-
Notifications
You must be signed in to change notification settings - Fork 27
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
chore: update jest #1263
chore: update jest #1263
Changes from all commits
e535ad9
4b54312
e5306e5
506b595
0d59207
d16784a
76c8b70
1b88ecb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,6 @@ declare namespace jest { | |
toRender(component: React.ComponentType): R; | ||
toHaveState(selector: string, expected: unknown): R; | ||
// The following matchers are part of https://www.npmjs.com/package/jest-dom | ||
toBeInTheDocument: () => R; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, good to know! |
||
toHaveText(selector: string): R; | ||
} | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -67,9 +67,9 @@ | |
] | ||
}, | ||
"devDependencies": { | ||
"@commercetools/github-labels": "1.1.0", | ||
"@commercetools-docs/writing-style": "1.0.3", | ||
"@commercetools-uikit/design-system": "10.13.0", | ||
"@commercetools/github-labels": "1.1.0", | ||
"@commitlint/cli": "8.3.5", | ||
"@commitlint/config-conventional": "8.3.4", | ||
"@graphql-codegen/add": "1.11.2", | ||
|
@@ -93,16 +93,16 @@ | |
"@types/node": "12.12.25", | ||
"@types/node-fetch": "2.5.4", | ||
"@types/prop-types": "15.7.3", | ||
"@types/react": "16.9.17", | ||
"@types/react-dom": "16.9.4", | ||
"@types/react": "16.9.18", | ||
"@types/react-dom": "16.9.5", | ||
"@types/react-modal": "3.10.4", | ||
"@types/react-redux": "7.1.6", | ||
"@types/react-router": "5.1.4", | ||
"@types/react-router-dom": "5.1.3", | ||
"@types/webpack": "4.41.2", | ||
"@types/webpack": "4.41.3", | ||
"@types/webpack-env": "1.15.0", | ||
"@typescript-eslint/eslint-plugin": "2.16.0", | ||
"@typescript-eslint/parser": "2.16.0", | ||
"@typescript-eslint/eslint-plugin": "2.17.0", | ||
"@typescript-eslint/parser": "2.17.0", | ||
"apollo-server-errors": "2.3.4", | ||
"babel-eslint": "10.0.3", | ||
"babel-plugin-import-graphql": "2.7.0", | ||
|
@@ -128,14 +128,13 @@ | |
"eslint-plugin-prettier": "3.1.2", | ||
"eslint-plugin-react": "7.18.0", | ||
"eslint-plugin-react-hooks": "2.3.0", | ||
"eslint-plugin-testing-library": "1.4.1", | ||
"eslint-plugin-testing-library": "1.5.0", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I forgot to do it last time, we need to explicitly enable More on the reasons here: testing-library/eslint-plugin-testing-library#59 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. FYI: we're replacing that rule with a new one, targeted only for cases when you want to assert that an element is not in the document. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A good to now. Thanks for sharing 76c8b70. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, interesting. Read up on the background now. Makes sense what's in store there :) |
||
"faker": "4.1.0", | ||
"gatsby-plugin-emotion": "4.1.21", | ||
"graphql-cli": "3.0.14", | ||
"husky": "4.0.10", | ||
"xhr-mock": "2.5.1", | ||
"jest": "24.9.0", | ||
"jest-each": "24.9.0", | ||
"husky": "4.2.0", | ||
"jest": "25.1.0", | ||
"jest-each": "25.1.0", | ||
"jest-puppeteer": "4.4.0", | ||
"jest-runner-eslint": "0.7.5", | ||
"jest-runner-executor": "1.0.0", | ||
|
@@ -144,7 +143,7 @@ | |
"jest-watch-typeahead": "0.4.2", | ||
"lerna": "3.20.2", | ||
"lerna-changelog": "1.0.0", | ||
"lint-staged": "10.0.0", | ||
"lint-staged": "10.0.2", | ||
"mri": "1.1.4", | ||
"postcss": "7.0.26", | ||
"postcss-custom-properties": "9.0.2", | ||
|
@@ -154,28 +153,29 @@ | |
"rcfile": "1.0.3", | ||
"read-pkg-up": "7.0.1", | ||
"replace": "1.1.5", | ||
"rollup": "1.29.0", | ||
"rollup": "1.29.1", | ||
"rollup-plugin-babel": "4.3.3", | ||
"rollup-plugin-commonjs": "10.1.0", | ||
"rollup-plugin-node-builtins": "2.1.2", | ||
"rollup-plugin-node-resolve": "5.2.0", | ||
"rollup-plugin-peer-deps-external": "2.2.0", | ||
"rollup-plugin-postcss": "2.0.3", | ||
"rollup-plugin-postcss": "2.0.4", | ||
"rosie": "2.0.1", | ||
"shelljs": "0.8.3", | ||
"start-server-and-test": "1.10.6", | ||
"start-server-and-test": "1.10.7", | ||
"stylelint": "13.0.0", | ||
"stylelint-config-prettier": "8.0.1", | ||
"stylelint-config-standard": "19.0.0", | ||
"stylelint-order": "4.0.0", | ||
"stylelint-value-no-unknown-custom-properties": "2.0.0", | ||
"typescript": "3.7.5", | ||
"vfile-message": "2.0.2" | ||
"vfile-message": "2.0.2", | ||
"xhr-mock": "2.5.1" | ||
}, | ||
"resolutions": { | ||
"@commercetools-frontend/ui-kit": "10.13.0", | ||
"**/@commercetools-frontend/ui-kit": "10.13.0", | ||
"@types/react": "16.9.17", | ||
"@types/react": "16.9.18", | ||
"@types/react-router": "5.1.4", | ||
"react": "16.12.0", | ||
"**/react": "16.12.0", | ||
|
@@ -189,4 +189,4 @@ | |
"npm": ">=5", | ||
"yarn": ">=1.10" | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we consider this a breaking change? Cause the jest peer dep also needs to be bumped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for raising. I think to me it's not a breaking change. Only node 6 support is dropped and we require node 10/12 in other cases already. All other breaking changes I see are dependent to how people use jest within our peer dependency range. So if somebody imported from
@jest/core
orjest-cli
and that now changed is not something we can make guarantees about. If their remain to have 24 installed nothing would break for them in anyway. Do you agree or have other concerns about this?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah if we support both version it should be fine like this. Let's maybe mention it in the changelog that people can start using jest 25.