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

429 - Upgrade to Nextjs 13 / Yarn 3 / Storybook #432

Merged
merged 20 commits into from
Sep 13, 2023

Conversation

nozomione
Copy link
Member

@nozomione nozomione commented Sep 13, 2023

Issue Number

Closing #429

Purpose/Implementation Notes

The following changes were made in this PR:

  • Upgraded the node docker image v14.17 to v18.17.1
  • Migrated the storybook v6 to v7
  • Migrated the Next.js v11 to v13
  • Upgrade Yarn v1 to v3 in project
  • Resolved the compile warnings/errors (please see commits for each warning/error)
  • Excluded ./yarn auto-generated directory from the pre-commit workflow (otherwise test will fail due to the trailing whitespace e3d361f)
  • Other adjustments due to the migrations

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

…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)
…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
@nozomione nozomione linked an issue Sep 13, 2023 that may be closed by this pull request
…revert back the test change (previous commit for removing the whitespace from auti-generated ./yarn/release) file
@nozomione nozomione marked this pull request as ready for review September 13, 2023 01:40
@nozomione nozomione self-assigned this Sep 13, 2023
Copy link
Contributor

@davidsmejia davidsmejia left a 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

@@ -11,6 +11,7 @@ DOCS_PORT=8001
# Client
STORYBOOK_PORT=7001
CLIENT_PORT=7000
NODE_IMAGE=node:18.17.1
Copy link
Contributor

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?

Copy link
Member Author

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!

@nozomione nozomione merged commit e81e9fa into dev Sep 13, 2023
3 of 4 checks passed
@nozomione nozomione deleted the nozomieone/429-upgrade-tech-stack branch September 13, 2023 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade to Nextjs 13 / Yarn 3 / Storybook
2 participants