-
Notifications
You must be signed in to change notification settings - Fork 212
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
Update nuxt, @nuxt/vue-app, @nuxt/types dependencies #3247
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great start!
You will need to run just node-install
at the root of the repository. This will update the lock file, pnpm-lock.yaml
. After you commit this file, the linting should be fixed.
@obulat After running |
I really don't understand why your lock file is updated, @khushi-kothari 😕 When I ran it locally on your branch, I got the following:
(I redacted the openverse file paths) I committed the lock file and pushed it to your branch. Other options to try are running |
Hm, it looks like the
|
Ok @obulat that is the next task and am updating vue dependencies. Why are some of the CI tests failing in the current PR? |
Thanks @obulat for adding lock file, I will look into what is causing this issue so next updates can be committed smoothly. |
The CI tests are failing because the |
@obulat Updated vue dependencies. Still 2 CI tests are failing. |
Weirdly, the lock file didn't fully match the updates in |
Hi, @khushi-kothari ! Thank you for creating the individual PRs. Could you please update them so that they only update the dependencies listed in the corresponding PR description? For instance, Update focus-trap dependency should only update
|
@khushi-kothari, for this particular PR, we will need to either debug the way that Storybook is run in the CI now that Webpack added a patch for SSL, and Nuxt has removed its own patch (which is causing the CI to fail currently), or remove the smoke test from the CI. I'll ask other maintainers and write more here later. |
Hey @obulat I think as it is linting problem always there is some issue while tracking whitespace changes. I locally have the following change for some reason it is not tracked while commiting. But while viewing it remotely, it is like this :
Yet, linting error is thrown. |
I am not sure what's happening with the whitespace changes and why are they not tracked...
|
Ya that will be very helpful @obulat as the process you described isn't working for me locally. I hope my contributions were helpful. As my first experience to open sourcing, I could say I will continue doing it and will grow in the process. Thankyou for being the kindest mentor and guiding me through this issue very calmly. |
Thank you for your contributions, @khushi-kothari, they are very helpful! Hope you can keep contributing with Openverse ❤️ |
Signed-off-by: Olga Bulat <[email protected]>
Signed-off-by: Olga Bulat <[email protected]>
@@ -21,6 +21,7 @@ | |||
"prod:playwright": "pnpm i18n:copy-test-locales && pnpm prod", | |||
"storybook": "nuxt storybook --port=54000", | |||
"storybook:build": "nuxt storybook build", | |||
"storybook:build-for-docs": "NODE_OPTIONS=--openssl-legacy-provider nuxt storybook build", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This script is run in GitHub CI runner (not Docker), and without openssl-legacy-provider
it fails.
Signed-off-by: Olga Bulat <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Fixes
Fixes #3242 by @obulat
Description
Updated nuxt dependency in
frontend/package.json
and updated the lock file, and commited the changes.Testing Instructions
Checklist
Update index.md
).main
) or a parent feature branch.Developer Certificate of Origin
Developer Certificate of Origin