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

chore: enforce file extensions on imports #6202

Merged
merged 5 commits into from Jul 13, 2020
Merged

Conversation

jackfranklin
Copy link
Collaborator

No description provided.

@@ -88,7 +89,8 @@ module.exports = {

"no-restricted-imports": ["error", {
patterns: ["*Events"],
}]
}],
"import/extensions": ["error", "ignorePackages"]
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

we need to figure out how packages work for a browser ESM build - but that's a separate issue to this one. I'll have a PR/issue up describing our potential approach later :)

scripts/ensure-correct-devtools-protocol-package.ts Outdated Show resolved Hide resolved
test/jshandle.spec.ts Outdated Show resolved Hide resolved
test/launcher.spec.ts Outdated Show resolved Hide resolved
To make our output agnostic it should include file extensions in the
output, as per the ESM spec. It's a bit odd for Node packages but makes
it easier to publish a browser build.
@jackfranklin jackfranklin merged commit ffec247 into main Jul 13, 2020
@jackfranklin jackfranklin deleted the enforce-file-extensions branch July 13, 2020 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants