fix: add babel entry to accommodate styles components #816
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
Signed-off-by: Brent Hoover <brent@thebuddhalodge.com>
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.
Signed-off-by: Brent Hoover brent@thebuddhalodge.com
Impact: minor
Type: bugfix
Issue
When switching to Node 14 get this error and some styles do not load:
PropclassNamedid not match. Server: "makeStyles-anchor-11" Client: "makeStyles-anchor-8Seems to be this issue
Solution
Add a section to babelrc that makes sure that class names are the same on client and server.
Breaking changes
None
Testing
yarn run start:dev