-
Notifications
You must be signed in to change notification settings - Fork 8
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
slow frontend upgrade #2260
Comments
Branched from next_release and tried to build frontend:
Creating an optimized production build... ./src/index.tsx npm ERR! code ELIFECYCLE npm ERR! A complete log of this run can be found in: |
to "fix" this I deleted node_modules in the container and re-ran npm run build which worked |
Upgraded RDRF node docker container from 10.16.3 to 18.12.0 |
NOT applying the updates above but just doing the following on Node 18.12.0 container rm -rf node_modules BUT npm run build fails with
npm run test passes but |
removed yarn.lock root@f07e75f8551f:/app/rdrf/rdrf/frontend# rm yarn.lock ran npm run test which now fails ..:
then tried npm run build and received permission error?
|
Given the build folder is not used in prod, should just make /data/frontendbuild for the bundles and change postbuild |
Adding prebuild action |
2 similar comments
Adding prebuild action |
Adding prebuild action |
Added prebuild step to build in /data/frontend/build ( where data is mounted as /data/dev in dev env. ran error:
|
yarn added postcss-safe-parser but this still failed as postcss-safe-parser is installed as a dep of react-scripts. shows how to update react-scripts from 4.0.3 to 5.0.1:
|
Now running :
|
odd behaviour: |
build runs |
build failed:
|
running ./develop.sh run "" node test |
So the travis build fails because the node user is uid 002 in travis not 001 as in dev so node can write the Yarn logfile in dev as my user is 001 |
At this commit the build passes because I've only upgraded react-scripts I've created a branch ncutest branched off rdrf-2260 where I upgrade using ncu to upgrade more This gave the dreaded Jest unexpected token error ( test suites wouldn't run) https://stackoverflow.com/questions/55493322/create-react-app-jest-encountered-unexpected-token this outlines a fix ( actually I saw here first https://dev.to/bytebodger/how-i-fixed-the-unexpected-token-error-in-jest-4o1j ) Now some tests are failing , I'll merge in and fix |
Build is at least running the tests .. https://app.travis-ci.com/github/muccg/rdrf/builds/257427283 |
Trying to upgrade using ncu caused major issues ( jest fails etc)
Will try a more targeted approach to fixing the dependabot issues
The text was updated successfully, but these errors were encountered: