Issue with frontend install via setup.bash #6
Comments
|
Hi Ashley,
Can you try removing ***@***.***' from the package.json, delete the
package-lock.json, and then run `npm install` and `npm run build` again
Thanks,
Campbell
…On Tue, Jun 27, 2023 at 9:51 AM Ashley Stewart ***@***.***> wrote:
The setup.bash script currently has:
#!/bin/bash
cd frontend
npm install
npm buildcd ..
cd api
sudo apt-get update
sudo apt-get install libsqlite3-dev
npm install sqlite3 --build-from-source
npm install
npm i -g ts-node
There is an issue with the frontend install inside the container on the npm
build step, where I get:
npm WARN build `npm build` called with no arguments. Did you mean to `npm run-script build`?
I tried doing as it suggested and using npm run-script build instead and
got:
> ***@***.*** build /opt/QSMxT-UI/frontend> react-scripts build
Creating an optimized production build...
One of your dependencies, babel-preset-react-app, is importing ***@***.***/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working ***@***.***/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it may break at any time.
babel-preset-react-app is part of the create-react-app project, which
is not maintianed anymore. It is thus unlikely that this bug will
ever be fixed. Add ***@***.***/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.
Failed to compile.
[eslint] Failed to load plugin ***@***.***' declared in 'package.json » eslint-config-react-app#overrides[0]': Cannot find module 'eslint/use-at-your-own-risk'
Require stack:
- ***@***.***/eslint-plugin/dist/util/getESLintCoreRule.js
- ***@***.***/eslint-plugin/dist/rules/block-spacing.js
- ***@***.***/eslint-plugin/dist/rules/index.js
- ***@***.***/eslint-plugin/dist/index.js
- ***@***.***/eslintrc/dist/eslintrc.cjs
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ***@***.*** build: `react-scripts build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ***@***.*** build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-06-26T23_53_10_135Z-debug.log
I wonder if you know what the solution here could be?
—
Reply to this email directly, view it on GitHub
<#6>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKDGFMJCP75YGI6PKQRJCVDXNIN6XANCNFSM6AAAAAAZU2QSTY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Thanks for the suggestion! I don't see the pattern ***@***.*** in the package.json file anywhere, but I tried removing the package-lock.json file. I get the same error with (base) root@2fbd9a25d898:/opt/QSMxT-UI/frontend# npm run build
> [email protected] build /opt/QSMxT-UI/frontend
> react-scripts build
Creating an optimized production build...
Failed to compile.
[eslint] Failed to load plugin '@typescript-eslint' declared in 'package.json » eslint-config-react-app#overrides[0]': Cannot find module 'eslint/use-at-your-own-risk'
Require stack:
- /opt/QSMxT-UI/frontend/node_modules/@typescript-eslint/eslint-plugin/dist/util/getESLintCoreRule.js
- /opt/QSMxT-UI/frontend/node_modules/@typescript-eslint/eslint-plugin/dist/rules/block-spacing.js
- /opt/QSMxT-UI/frontend/node_modules/@typescript-eslint/eslint-plugin/dist/rules/index.js
- /opt/QSMxT-UI/frontend/node_modules/@typescript-eslint/eslint-plugin/dist/index.js
- /opt/QSMxT-UI/frontend/node_modules/@eslint/eslintrc/dist/eslintrc.cjs
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `react-scripts build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-06-27T03_55_26_405Z-debug.log |
|
To help make this easier to debug, I've created a GitHub Action on this repository that automatically runs the setup.sh script on each commit. Could you look at the Action output to see where it is failing? This is the main GitHub Actions page. This is the most recent run with debug output. I also changed node from v12.13 to v14.17.0 (see the GitHub Actions workflow file that specifies it here. I changed this because I was getting a lot of warnings about packages that depended on the updated version, and there doesn't seem to be anything that specifically requires the older v12.13. |
|
I've made some progress on my fork of the repository - hopefully, I can solve this one soon. :) |
|
Hi Ashley,
I just updated the repo to include the build folder for the frontend, so
you don't have to run it during setup and get those errors you were
receiving.
I've updated the bash scripts to reflect this.
Let me know if you have any more issues.
Regards,
Campbell
…On Tue, Jun 27, 2023 at 4:45 PM Ashley Stewart ***@***.***> wrote:
I've made some progress on my fork <https://github.com/QSMxT/QSMxT-UI> of
the repository - hopefully, I can solve this one soon. :)
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKDGFMPIHZVIPXI3VRD64PLXNJ6QVANCNFSM6AAAAAAZU2QSTY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
setup.bashscript currently has:There is an issue with the frontend install inside the container on the
npm buildstep, where I get:I tried doing as it suggested and using
npm run-script buildinstead and got:I wonder if you know what the solution here could be?
The text was updated successfully, but these errors were encountered: