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

Production Deploy #433

Merged
merged 2 commits into from
Sep 14, 2023
Merged

Production Deploy #433

merged 2 commits into from
Sep 14, 2023

Conversation

davidsmejia
Copy link
Contributor

@davidsmejia davidsmejia commented Sep 14, 2023

  • Updates to client
    • upgrade to nextjs13 / yarn3 / storybook 7
    • removes call to contribute banner

* remove warning 'Received 'true' for a non-boolean attribute crossOrigin' at compile time

* remove the flag deprecation warning '--static-dir CLI flag is deprecated’ at compile time

* remove the error 'TypeError: Cannot read property 'definitions' of undefined’ at compile

* remove the performance warning ‘Reverting webpack devtool to 'eval-source-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)

* upgrade node image to v18.17.1 (stored the node image to the enviromental variable)

* upgrade the storybook to v7 from v6

* (fix) resolve runtime error 'MyDocument.getInitialProps() should resolve to an object with a html'

* (fix) add the legacyBehavior prop to Next.js buit-in Link component

* (fix) remove the warning 'The value at .experimental has an unexpected property, productionBrowserSourceMaps, which is not in the list of allowed propertie'(no longer the property of experiment) at compile

* (fix) resolve 'Warning: A title element received an array with more than 1 element as children' at compile by updating the PageTitle component JSX

* (fix) resolve the datatype warning ‘Failed prop type: Invalid prop  supplied to , expected one of type [string]’ at compile

* upgrade Yarn to latest stable v3.6.3 from v1.22.19 and add a local .gitignore file in the client directory for Yarn none-zero-installs instead of editing .gitignore in the root

* (edit) specified Yarn version in the docker compose

* (fix) remove ‘RESOURCE-NAME’ undefined errors at the runtime (storybook):
- 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

* remove trailing white space and add new line at the end in .gitignore

* remove trailing whitespace after the yarn set version command

* (test) remove trailing whitespace inauto-generate file ./yarn/release

* (edit) exclude .yarn (auto-generated files) from pre-commit test and revert back the test change (previous commit for removing the whitespace from auti-generated ./yarn/release) file

* (edit) use module import, add addons, and rearrange the properties in alphabetical order

* (edit) remove the env var for the docker node image and hard-code in the docker compose file
* (edit) unrender the contribution banner from UI (so that we can toggle back the banner as required in the future)

* create the ContributePageCard and render in the contribute page

* (edit) remove the download guideline as PDF button and delete the PFD file in /src/public

* (edit) update the URL for contribute_hsform and delete the contribute_pdf (for previously deleted PDF file) property

* (edit) rename ContributePageCard to WarningCard and define props and add the dropshadow

* (edit) add the WarningCard to the contirbute page instead of Layout
@davidsmejia davidsmejia merged commit 0507899 into main Sep 14, 2023
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants