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

Upgrades Next.js from 8.x.x to 9.x.x #512

Merged
merged 1 commit into from
Oct 4, 2019
Merged

Upgrades Next.js from 8.x.x to 9.x.x #512

merged 1 commit into from
Oct 4, 2019

Conversation

jessicamarcus
Copy link
Contributor

This PR is based on #458 and upgrades Next.js to latest across all apps except for 311; after upgrading (along with Babel from 7.1.x to 7.6.x), running Jest throws

[mobx] Encountered an uncaught exception that was thrown by a reaction or observer component, in: 'Reaction[RecentRequestRow#3350.render()] { Invariant Violation: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

Since 311 is not currently in production and it’s unknown whether it ever will be, it was decided to leave it as-is for the time being rather than spend more time troubleshooting.

@@ -11,7 +11,7 @@ import yar from 'yar';
import cleanup from 'node-cleanup';
import acceptLanguagePlugin from 'hapi-accept-language2';
import hapiDevErrors from 'hapi-dev-errors';
import next from 'next';
const next = require('next');
Copy link
Contributor

@phillipbentonkelly phillipbentonkelly Sep 26, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hadn't seen require and import mixed in the same file before. Is this required for the new version of Next, I see the same change in another file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You know, I was following Fiona’s lead with the PR she made in preparation for this, but I didn’t actually test whether this syntax is necessary anymore... I’ll do so and update the PR.

Copy link
Contributor

@phillipbentonkelly phillipbentonkelly Sep 26, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, no prob. I don't see it as it blocker if it's working. I would guess, if turning require into an import still works then I'd chuck-it to her just forgetting/copy-pasting. I'd done the same plenty of times lol. Just had the Q 💃

Copy link
Contributor

@phillipbentonkelly phillipbentonkelly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, left a question.

@jessicamarcus jessicamarcus merged commit b84e13b into develop Oct 4, 2019
@jessicamarcus jessicamarcus deleted the update-next branch October 4, 2019 14:59
@phillipbentonkelly phillipbentonkelly restored the update-next branch August 4, 2021 14:15
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