Comments (3)
Great to see it's working for you!
As you can see, you are using a little bit to new version of node, I think in the docs it's even written that dashy needs the latest LTS version which is currently 20.x.x, but as you can see it even works with newer version, just with that note.
I think --ignore-engines was introduced to fix some dependency issue when upgrading some of them to more up-to date versions, but not entirely sure on that.
from dashy.
error: Your local changes to the following files would be overwritten by merge:
public/conf.yml
yarn.lock
Please commit your changes or stash them before you merge.
Aborting
This suggests that changes to the file conf.yml and yarn.lock are not made because they are different on your system than on the git repo.
But yarn.lock needs to be changes as there were changes in dependencies and upgrading them.
Please make a copy of conf.yml (and possibly other assets like images that you saved inside dashy) and remove the whole dashy folder and clone the repo again.
That is probably the easiest.
Otherwise save a copy of conf.yml and assets and run 'git reset --hard'
from dashy.
error: Your local changes to the following files would be overwritten by merge: public/conf.yml yarn.lock Please commit your changes or stash them before you merge. Aborting
This suggests that changes to the file conf.yml and yarn.lock are not made because they are different on your system than on the git repo.
But yarn.lock needs to be changes as there were changes in dependencies and upgrading them.
Please make a copy of conf.yml (and possibly other assets like images that you saved inside dashy) and remove the whole dashy folder and clone the repo again. That is probably the easiest. Otherwise save a copy of conf.yml and assets and run 'git reset --hard'
oh sry maybe I had to be more clear, I meant the warnings, not the errors :) Last ones are absolutly clear.
this part here:
root@dashy:/opt/dashy# npm install --ignore-engines
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16.0.0 <21.6.2' },
npm WARN EBADENGINE current: { node: 'v21.7.1', npm: '10.5.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@achrinza/[email protected]',
npm WARN EBADENGINE required: { node: '8 || 10 || 12 || 14 || 16 || 17' },
npm WARN EBADENGINE current: { node: 'v21.7.1', npm: '10.5.0' }
npm WARN EBADENGINE }
oh... with the git reset --hard
did the trick, thank you!
EDIT: OFC I know that I use the ignore-engines part in my npm install command, but this was due to other issue I hade here before. But isn't it possible to update those requriements to latest versions as well or is this a more complicated stuff that needs to much time to do it for each update on node
?
It is running with those versions, already tested right now :)
from dashy.
Related Issues (20)
- [FEATURE_REQUEST] Hide city details for the Public IP widget
- [FEATURE_REQUEST] Add a direct link to the repository displayed in the GitHub Profile Stats widget HOT 2
- [BUG] Public Holidays widget returns Invalid Date on Safari HOT 2
- [BUG] Missing Fonts? HOT 7
- [BUG] Cant install dashy from Lissy93/portainer-templates in portainer HOT 4
- [BUG] Dashy 3.0.0 not loading despite complete build HOT 31
- [BUG] OpenID redirect not triggered for index.html HOT 6
- Dashy Latest 3.00 Does not Work HOT 2
- [QUESTION] dockerfile command may need run `yarn start` not `yarn build-and-start`? HOT 4
- [BUG] pageInfo.title no longer displayed in browser tab HOT 3
- [BUG] Outdated Docs HOT 3
- [BUG] <Collapsed setting persistant over diffrent pages> HOT 2
- [QUESTION] Something related to the status check of self-signed https services HOT 17
- use the latest version for component : v8:5.5.5 HOT 3
- [BUG] Widgets are not sending X-Api-Key and Authorization headers HOT 7
- [QUESTION] hideForKeycloakUsers not working HOT 2
- [BUG] Dashy not working again HOT 8
- [FEATURE_REQUEST] Hide Settings from Guests and Specific users HOT 5
- [BUG] Sharing Keycloak setup, not exactly a bug but certainly felt like one HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dashy.