Errant frontend/node_modules dir checked into repo #1

New Issue

ecliptik · 2021-06-18T23:29:51Z

ecliptik commented

2021-06-18 23:29:51 +00:00

When trying to build and install goldberry it gives the error npm ERR! code ELIFECYCLE.

Removing the frontend/node_modules directory and re-trying the build works.

Full error:

🚀➜ make
wails build                                                                                                                                                                                                   
Wails v1.16.3 - Building Application                                                                                                                                                                          
                                                      
✓ Skipped frontend dependencies (-f to force rebuild)
⢿ Building frontend...npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.                                                                                                                                    
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
npx: installed 73 in 4.497s                                      
CLI for webpack must be installed.
  webpack-cli (https://github.com/webpack/webpack-cli)           
         
We will use "npm" to install the CLI via "npm install -D webpack-cli".
Do you want to install 'webpack-cli' (yes/no): npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! vanilla@ build: `npx webpack`
npm ERR! Exit status 1
npm ERR!                                                               
npm ERR! Failed at the vanilla@ 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!     /home/micheal/.npm/_logs/2021-06-18T23_24_35_755Z-debug.log

When trying to build and install goldberry it gives the error `npm ERR! code ELIFECYCLE`. Removing the `frontend/node_modules` directory and re-trying the build works. Full error: ``` 🚀➜ make wails build Wails v1.16.3 - Building Application ✓ Skipped frontend dependencies (-f to force rebuild) ⢿ Building frontend...npm WARN npm npm does not support Node.js v10.24.0 npm WARN npm You should probably upgrade to a newer version of node as we npm WARN npm can't make any promises that npm will work with this version. npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. npm WARN npm You can find the latest version at https://nodejs.org/ npx: installed 73 in 4.497s CLI for webpack must be installed. webpack-cli (https://github.com/webpack/webpack-cli) We will use "npm" to install the CLI via "npm install -D webpack-cli". Do you want to install 'webpack-cli' (yes/no): npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! vanilla@ build: `npx webpack` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the vanilla@ 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! /home/micheal/.npm/_logs/2021-06-18T23_24_35_755Z-debug.log ```

asdf commented

2021-06-19 00:27:19 +00:00

Had this same issue and was able to work around it using the provided fix of removing directory frontend/node_modules

Had this same issue and was able to work around it using the provided fix of removing directory `frontend/node_modules`

sloum commented

2021-06-19 02:49:13 +00:00

So weird. I had also gotten that issue and had removed node_modules from version control... but it doesnt seem to have worked. I just pushed again after a second pass at removal.

Glad y'all got it to build! It is admittedly not the most featureful graphical gemini client and I mostly just wanted to play around with gui stuff in go... though it ended up being a lot of js, lol. I wish there were more mature go specific gui packages (rather than gtk wrappers and the like). That said, for anyone that doesnt mind js/css and wanting to do graphics programming in go this framework worked really well for me and had a good development flow to it. There are a few things I wish it did, but doesnt... but that is ok. I mostly worked them out.

So weird. I had also gotten that issue and had removed node_modules from version control... but it doesnt seem to have worked. I just pushed again after a second pass at removal. Glad y'all got it to build! It is admittedly not the most featureful graphical gemini client and I mostly just wanted to play around with gui stuff in go... though it ended up being a lot of js, lol. I wish there were more mature go specific gui packages (rather than gtk wrappers and the like). That said, for anyone that doesnt mind js/css and wanting to do graphics programming in go this framework worked really well for me and had a good development flow to it. There are a few things I wish it did, but doesnt... but that is ok. I mostly worked them out.

👍 2

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sloum/goldberry#1