Skip to content

Conversation

dmz-v-x
Copy link
Contributor

@dmz-v-x dmz-v-x commented Oct 2, 2024

Type of Change:

Tool Source: JS

What issue does this relate to?

This PR resolves #454.

What should this PR do?

  • Removed all esm + extensionless usages from the project.
  • Updated ESLint configuration to enforce file extensions in import statements.
  • Ensured all imports in the project now include proper file extensions.
  • Updated the project’s package.json to set "type": "module".
  • Updated the year in the copyright header for all modified files.

What are the acceptance criteria?

  • No remaining extensionless imports.
  • ESLint configuration correctly enforces file extensions.
  • Copyright headers are updated.

Feedback:
Please review and let me know if any further adjustments are required. Thank you!

@MattIPv4
Copy link
Contributor

MattIPv4 commented Oct 2, 2024

👋 Just as an FYI for the future, you don't need to create a new PR to make changes to it, you should just push to your existing PR. cc #485

@MattIPv4 MattIPv4 changed the title "Fix #454: Enforce file extensions in imports, remove ESM usages, update copyright headers" Enforce file extensions in imports to comply with ESM standards Oct 2, 2024
@dmz-v-x
Copy link
Contributor Author

dmz-v-x commented Oct 3, 2024

👋 I've made the requested changes regarding the copyright headers and reverted unnecessary modifications. Please review when you have a chance. Thank you!

Copy link
Contributor

@MattIPv4 MattIPv4 left a comment

Choose a reason for hiding this comment

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

LGTM, tyvm for all the work on this

@MattIPv4 MattIPv4 merged commit b893df3 into digitalocean:master Oct 4, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use proper ESM imports w/ extensions
2 participants