-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
feat: replace relative import closes #5484 #5487
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Thanks for the PR. I think this on the right track but these changes have broken storybook. Can you please have a look at this: https://github.com/nodejs/nodejs.org/actions/runs/5499772573/jobs/10027807119?pr=5487
I have fixed the test issue but there is 1 snapshot test that is failing and I don't know whats causing it may be we need to record a new snapshot need assistance on this |
Can you first rebase your branch? We did a few changes on some files that are conflicting. Now, to update the snapshots you can simply run |
📦 Next.js Bundle Analysis for nodejs.orgThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
FYI rebasing seems to be needed! |
Signed-off-by: Umair Raza <[email protected]>
Used below command to revert back to the `build-and-analysis.yml` file ```bash git checkout main -- .github/workflows/build-and-analysis.yml ```
@umairraza96 could we do the rebasing or recreation once more? And then I'll prioritise getting this merged so that you don't need to worry about further rebases/updates! 🙇 |
@@ -46,7 +46,7 @@ jobs: | |||
~/.npm | |||
.next/cache | |||
node_modules/.cache | |||
key: cache-${{ hashFiles('package-lock.json') }} |
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.
Unrelated changes again over here :S
@@ -1 +1 @@ | |||
[] |
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.
Also unrelated changes here
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.
Why we don’t put this file in gitinignore ?
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 was already discussed before. And the file should not be on gitignore. (Also adding it right now would have 0 effects)
I see, you could simply have deleted this one, rebranch from main and force push, so that you wouldn’t need to create a new PR 🙈 But that’s okay, let’s close this one! |
Closing in favor of #5513 |
Description
Added a plugin for eslint
eslint-plugin-no-relative-import-paths
Related Issues
Check List
npx turbo lint
to ensure the code follows the style guide. And runnpx turbo lint:fix
to fix the style errors if necessary.npx turbo format
to ensure the code follows the style guide.npx turbo test
to check if all tests are passing, and/ornpx turbo test:snapshot
to update snapshots if I created and/or updated React Components.