Closed loiiiic closed 1 year ago
Hello,
I have continued to investigate and can now run the npm ci
command and npm run build
.
To do this, I uninstalled the node.JS v18.1.0 version with :
nvm uninstall v18.1.0
Then install the node.JS LTS version (16.15.0) with :
nvm install --lts
If you installed LTS on Windows10 and run into the same error, you can also try the following: npm ci --save --legacy-peer-deps You have to install legacy-peer-deps before.
i do actually have the same issue where i am building a ci for a project i want to try out: https://github.com/ss89/Ferraris_MQTT_Energy_Counter_Meter_TCRT5000/actions/runs/3244592852/jobs/5320967950
I did switch from node 18 to node 16, but it doesn't seem to make a difference.
Any suggestions what to try? I actually want to contribute to your project with this @Eisbaeeer :-D
switching down to node 14 actually seemed to fix the issue. interesting.
I don't see a PR mentioned, how was this fixed?
@ss89 See 3a39b7ae3282e38cbc7f3f971e5c236c0d646e77
Thank you 👍🏻
Hello,
I have just implemented your framework with the standard configuration and everything works perfectly. Thanks for the great work!
The next step for me is to customize the html file. For that, I did the following actions:
Installation of Node Version manager :
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash
Installation of npm and node :
nvm install node
Open a terminal in /xxx/.pio/libdeps/d1_mini/ESP8266 IoT Framework and run :
npm ci
but I get this output :
Not being familiar with npm, but I guess it's a versioning issue between the packages associated with NPM on my computer and those requested by your framework. What is good practice in this case?
Thank you!