fix(toolkit pro): fix two issues of toolkit/pro after pre-publish#23
Merged
h-ivy merged 1 commit intoopentiny:devfrom Apr 20, 2023
fengyon:fengyon/fix-pro-depencies
Merged
fix(toolkit pro): fix two issues of toolkit/pro after pre-publish#23h-ivy merged 1 commit intoopentiny:devfrom fengyon:fengyon/fix-pro-depencies
h-ivy merged 1 commit intoopentiny:devfrom
fengyon:fengyon/fix-pro-depencies
Conversation
fengyon
changed the title
h-ivy
approved these changes
Apr 20, 2023
1. fix no `inquirer` dependency in package.json. 2. fix no `tsconfig.spec.json` file in toolkit/pro/tempalte/tinyng.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
PR
修复pro套件预发布后验证发现的问题
1、package.json中没有
inquirer依赖2、template/tinyng发布后缺少了
tsconfig.spec.json文件PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information