-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
429 - Upgrade to Nextjs 13 / Yarn 3 / Storybook #432
Conversation
…in' at compile time
…ated’ at compile time
…defined’ at compile
…urce-map'. Changing the webpack devtool in development mode will cause severe performance regressions’ at compile by removing the custom devtool override in next.config since it reverts back to eval-source-map during the compilation (ref: https://nextjs.org/docs/messages/improper-devtool)
…lve to an object with a html'
…d property, productionBrowserSourceMaps, which is not in the list of allowed propertie'(no longer the property of experiment) at compile
…han 1 element as children' at compile by updating the PageTitle component JSX
…pplied to , expected one of type [string]’ at compile
…itignore file in the client directory for Yarn none-zero-installs instead of editing .gitignore in the root
…ok): - add the alias for the data directory for import - adjust the data and remove unused resource files - update the stories based on the above changes
…revert back the test change (previous commit for removing the whitespace from auti-generated ./yarn/release) file
… alphabetical order
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great just one comment
docker-compose.env
Outdated
@@ -11,6 +11,7 @@ DOCS_PORT=8001 | |||
# Client | |||
STORYBOOK_PORT=7001 | |||
CLIENT_PORT=7000 | |||
NODE_IMAGE=node:18.17.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is necessary. I could kinda see an argument for it if we used it in multiple places but I would expect to find the version of the container I am running in docker-compose.yml
. If it is all the same could we keep it in that file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, let's remove it then!
…the docker compose file
Issue Number
Closing #429
Purpose/Implementation Notes
The following changes were made in this PR:
v14.17
tov18.17.1
v6
tov7
v11
tov13
v1
tov3
in project./yarn
auto-generated directory from the pre-commit workflow (otherwise test will fail due to the trailing whitespace e3d361f)Types of changes
Checklist