-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update all dependencies assumed to be compatible #173
Conversation
…semver This leaves four available dependencies unmerged as they have breaking changes (indicated by semver): Package Current Wanted Latest Package Type URL bootstrap 3.4.1 3.4.1 4.3.1 dependencies https://getbootstrap.com/ eslint-config-xo-typescript 0.19.0 0.19.0 0.21.0 devDependencies https://github.com/xojs/eslint-config-xo-typescript#readme nock 9.6.1 9.6.1 11.7.0 devDependencies https://github.com/nock/nock#readme react-jsonschema-form 1.8.0 1.8.0 2.0.0-alpha.1 dependencies https://github.com/mozilla-services/react-jsonschema-form#readme
@matthieu-foucault this fails due to vercel/next.js#5318 |
|
Either way, renaming it to |
I'll update |
I think we want the next config for dotenv support? Would be nice to remove cssmodules support if we're not using them now–they're super buggy (as we discovered) and don't play nice with |
Maybe just rename the config for now then. |
During the great typescript refactor, this file was renamed as typescript but next.js doesn't support a typescript config file. Partial revert of 61bf076
42704f6
to
3397428
Compare
@matthieu-foucault looks like there type errors caused by adding Are you good to take that or shall I? |
I can take a look. Looks like next is ignoring our |
Looks like we were using an unsupported feature with the { /*
// @ts-ignore something
*/ } pattern, since there's still an open issue about it |
Use of `@ts-ignore` in jsx expressions is unsupported. Somehow it works anyway in [email protected] so we need to pin until we've resolved the ignore comments. Example of unsupported comment: ``` { /* // @ts-ignore something */ } ``` see microsoft/TypeScript#31147
Sound good. I can see about fixing those errors and upgrading TypeScript in another PR. |
This leaves four available dependencies unmerged as they have breaking
changes (indicated by semver):
^ use
yarn outdated
to verifyThis closes a bunch of dependabot PRs.