We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Cool package! thanks for publishing!
Given this dir structure in a package root, I want to ensure that exports includes all of those files.
exports
elements ├── pf-accordion │ ├── pf-accordion-header.js │ ├── pf-accordion.js │ └── pf-accordion-panel.js ├── pf-avatar │ └── pf-avatar.js ├── pf-badge │ └── pf-badge.js └── pf-tooltip └── pf-tooltip.js 20 directories, 26 files
So linting with an option like exportGlobs: ['elements/*/pf-*.js'],
exportGlobs: ['elements/*/pf-*.js']
This "exports" field should fail
"exports"
{ '.': './pfe.js' }
and this one should pass:
{ '.': './pfe.js', './pf-accordion/pf-accordion-header.js': './pf-accordion/pf-accordion-header.js', './pf-accordion/pf-accordion-panel.js': './pf-accordion/pf-accordion-panel.js', './pf-accordion/pf-accordion.js': './pf-accordion/pf-accordion.js', './pf-avatar/pf-avatar.js': './pf-avatar/pf-avatar.js', './pf-badge/pf-badge.js': './pf-badge/pf-badge.js', './pf-tooltip/pf-tooltip.js': './pf-tooltip/pf-tooltip.js' }
The text was updated successfully, but these errors were encountered:
Hi, I'm not really sure what you're requesting here, how does
work? I did notice though that I didn't handle glob subpath patterns with multiple * (only supports one * now), maybe you're referring to this issue?
*
Sorry, something went wrong.
No branches or pull requests
Cool package! thanks for publishing!
Given this dir structure in a package root, I want to ensure that
exports
includes all of those files.So linting with an option like
exportGlobs: ['elements/*/pf-*.js']
,This
"exports"
field should failand this one should pass:
The text was updated successfully, but these errors were encountered: