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

When backfill runs, if there are outputFolders that doesn't exist, ignore it #118

Closed
kenotron opened this issue Oct 30, 2019 · 1 comment · Fixed by #124
Closed

When backfill runs, if there are outputFolders that doesn't exist, ignore it #118

kenotron opened this issue Oct 30, 2019 · 1 comment · Fixed by #124

Comments

@kenotron
Copy link
Member

Currently, the backfill command fails if the resultant command does not generate the outputFolders listed. If we were to share this config with many packages within a monorepo, we would have very different configs for each package... because some may not generate all the output folders.

@kenotron
Copy link
Member Author

Just remembered another scenario: there are times that we would allow different args to be passed to a npm run build that would generate ESM folder vs COMMONJS folder. So, backfill.config.js should allow us to specify both as outputFolder and just ignore the unused outputFolder value.

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 a pull request may close this issue.

1 participant