Add JS wrapper to CSS to support Serverless target #297
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
iaincollins
added
bug
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/iaincollins/next-auth-docs/i7tswx2pr |
|
Published as |
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.
Resolves #281
Using the 'Serverless' target on in Next.js on some platforms does not work if you try to read in files at runtime that are not JavaScript or JSON (e.g. CSS files), as discussed in #281
To work around this issue, this script is a manual step that wraps the compiled CSS (e.g. used for sign in / error pages) that is output by PostCSS by n a JavaScript file that has the CSS embedded in it, and exports a function that returns that CSS as a string.
This way the CSS is included in a .js file and won't cause problems with the Serverless target.