fix: lose components types of components.d.ts #447
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #403
fix #419
options.dts
is unresolved, if the user not settingdts
then will returnundefined
(not default valuetrue
), so must be use from the resolved optionctx.options.dts
.ctx.generateDeclaration()
can't resolve the UI components (get from resolvers) on first call on startup dev server, whether UI components in thecomponents.d.ts
exists or not, will be removed on startup dev server.This PR changes to generate .d.ts file on startup server if
ctx.options.dts
is true and the file (likecomponents.d.ts
) exists.(Of course,
components.d.ts
will still be updated normally when adding, updating files or triggertransform
hook.)No fix:
components.d.ts
(before startup server):Start dev/preview server if no setting
options.dts
:Start dev/preview server if setting
options.dts
to true:Warning
Missing
VanRate
(and other UI components) component type, the #403, #419 both is this status.Apply PR (fixed):
components.d.ts
(before startup server):Start dev/preview server if no setting
options.dts
:Start dev/preview server if setting
options.dts
to true: