Upgrade to Next.js 12; drop custom deploy tooling #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/prairielearn/marketing/3tsqjgay5RJ3V9pGQmKbvnUAV7My |
nwalters512
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR bumps to the latest version of Next.js so that we can use
import img from './path/to/image.png'- this will be important for #14. Unfortunately I had to use a canary version of 12.0.4 so I could pick up the fix from vercel/next.js#31134, which was necessary for the way we use Bootstrap.This PR also removes the custom tooling that was previously used to deploy the site to AWS. We're now pointing
prairielearn.comandwww.prairielearn.comdirectly at the Vercel deployment, so we don't need to run this on AWS anymore.