-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Nimbus dependencies #9
Comments
You should install nimbus via I'll check if we can update some dependencies... |
I guess we need to recreate the patches, missing version in the patch name. |
@userquin This is happening even when running I have included a recording to show what's happening :
nimbus-install.mov |
You can ignore both warnings, I'm going to check both... |
Now it should be fine, i18n and nuxt schema warnings fixed on dev server |
Thanks @userquin, I can confirm the warnings are gone now! I'll keep the issue open to discuss upgradind the other dependencies, or finding alternatives/obsolete packages. |
Renovate is configured for Elk: elk-zone/elk#1098, which periodically scans outdated dependencies and creates PRs. I think we can set up Renovate for nimbus too. Currently, some of them fail CI check so we need to adjust the existing codebase to align with package version up. |
@shuuji3 If Renovate was working fine for Elk then let's not reinvent the wheel, agreed. Who could setup Renovate on this repo then ? I guess it must be someone with admin rights ? |
Yes, the admin permission is needed as it requires installing the Renovate app (https://github.com/marketplace/renovate) to the repository (@patak-dev or someone who has proper permission can do that). We already codified the Renovate setting here so it would be easier to replicate the same setting as Elk instead of setting up from scratch: https://github.com/nimbus-town/nimbus/blob/main/.github/renovate.json5 |
Dependencies and packages
Since the project is not starting from scratch, there is already a lot of dependencies installed with a specific version. Now might be a good time to revisit what we are using and if there some upkeep needed or not.
In general
unimport
anywhere, AFAIK we just rely on Nuxt for autoimports ?)On
pnpm i
Executing
pnpm i
in the root of the project shows a warning in the console :Note
This has been solved in #10
On
pnpm dev
Executing
pnpm dev
shows two warnings in the console :Note
This has been solved in #13
On
pnpm outdated
Running
pnpm outdated
shows that a lot of the dependencies could be updated :The text was updated successfully, but these errors were encountered: