Skip to content
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

fix: use valid import/export syntax #2563

Merged
merged 2 commits into from
Apr 9, 2024
Merged

fix: use valid import/export syntax #2563

merged 2 commits into from
Apr 9, 2024

Conversation

kyubisation
Copy link
Contributor

Previously we were using the common syntax of importing/exporting files without the extension. However, this is not natively supported in browsers and also not in Node.js with ESM. This change adds a linting rule that automatically adds the .js extension
to any relative import.

Previously we were using the common syntax of importing/exporting files without
the extension. However, this is not natively supported in browsers and also not in Node.js
with ESM. This change adds a linting rule that automatically adds the .js extension
to any relative import.
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (main@3268c79). Click here to learn what that means.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2563   +/-   ##
=======================================
  Coverage        ?   93.22%           
=======================================
  Files           ?      308           
  Lines           ?    25309           
  Branches        ?     2047           
=======================================
  Hits            ?    23594           
  Misses          ?     1683           
  Partials        ?       32           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@jeripeierSBB jeripeierSBB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked every single file to ensure that everything is correct to finally see at the end of the PR that there is a new linting rule :P

@github-actions github-actions bot added the pr: lead review approved Pull request has been approved by a lead review label Apr 9, 2024
Copy link
Contributor

@TomMenga TomMenga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍
I think you broke the record for most changed files in a pr

@github-actions github-actions bot added pr: peer review approved Pull request has been approved by a peer review and removed pr: peer review required A peer review is required for this pull request labels Apr 9, 2024
@kyubisation
Copy link
Contributor Author

LGTM 👍 I think you broke the record for most changed files in a pr

I'm torn between being proud and distraught 😅

@kyubisation kyubisation merged commit 585cfc5 into main Apr 9, 2024
30 checks passed
@kyubisation kyubisation deleted the fix-valid-extensions branch April 9, 2024 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr: lead review approved Pull request has been approved by a lead review pr: peer review approved Pull request has been approved by a peer review preview-available
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants