-
Notifications
You must be signed in to change notification settings - Fork 421
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
docs(config): update updating guide for transformAliasedImportPaths #1128
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
f9ff307
to
97d0c67
Compare
3c7002e
to
8e949d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are your thoughts on removing the flags specifically for dist
and dist-collection
and having all of the transform behavior driven by the top-level config flag? I think it's confusing having them at different levels
docs/output-targets/dist.md
Outdated
:::tip | ||
If using the `dist-collection` output target directly, the same result can be achieved using the `transformAliasedImportPaths` flag on the target's config. | ||
If using the `dist-collection` output target directly, the same result can be achieved using the [`transformAliasedImportPaths`](../config/01-overview.md#transformaliasedimportpaths) flag on the target's config. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link points to the top-level config flag not the one for the dist-collection
target specifically.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 4090dda
I think it's probably the right move, but I think we're a little too close to the release to change this right now. I think enabling them by default will mitigate this a little bit (it's just "on"), and something I'd be interested in coalesing for v5 |
this commit updates the upgrade guide for stencil v4 to include new default values for `transformAliasedImportPaths` and `transformAliasedImportPathsInCollection`. STENCIL-829
4090dda
to
1cfaa11
Compare
this commit updates the upgrade guide for stencil v4 to include new default values for
transformAliasedImportPaths
andtransformAliasedImportPathsInCollection
.STENCIL-829
Core PR: stenciljs/core#4418