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(package): Allow deep imports from parse5 #453

Merged
merged 1 commit into from
Mar 16, 2022
Merged

Conversation

fb55
Copy link
Collaborator

@fb55 fb55 commented Mar 13, 2022

The generate-parser-feedback-test script currently fails due to deep imports from parse5 not being allowed. I assume this will apply to all submodules that currently have deep imports.

For now, let's allow deep imports of all files within parse5.

The `generate-parser-feedback-test` script currently fails due to deep imports from `parse5` not being allowed. I assume this will apply to all submodules that currently have deep imports.

For now, let's allow deep imports of all files within `parse5`.
@fb55 fb55 merged commit e41d774 into master Mar 16, 2022
@fb55 fb55 deleted the fix-dist-imports branch March 16, 2022 18:17
},
"./dist/*": {
"import": "./dist/*",
"require": "./dist/cjs/*"
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think that this is an anti-pattern.
The export map allows for an “allow-list” of what APIs to export as separate entry points, that is unrelated to the file system.
I believe we should carefully choose to expose what we want folks to use instead of exposing the whole file system?

Perhaps the problem in that script can be solved in a different way?

jmbpwtw pushed a commit to jmbpwtw/parse5 that referenced this pull request Feb 16, 2023
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.

3 participants