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

fix: Remove old @microsoft/recognizers-text-number version with postinstall scripts #4608

Merged
merged 3 commits into from
Jan 24, 2024

Conversation

JhontSouth
Copy link
Collaborator

#minor

Description

This PR removes the old version or @microsoft/recognizers-text-number from the other recognizers packages that require it.

Specific Changes

  • Added postinstall scripts in botbuilder-dialogs and botbuilder-dialogs-adaptive package.json files to remove the old version of @microsoft/recognizers-text-number.

Testing

These images show the dependencies tree before and after running the postinstall scripts.
image

@JhontSouth JhontSouth requested a review from a team as a code owner January 23, 2024 13:36
@coveralls
Copy link

coveralls commented Jan 23, 2024

Pull Request Test Coverage Report for Build 7626548897

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 84.477%

Totals Coverage Status
Change from base Build 7587095843: 0.0%
Covered Lines: 20411
Relevant Lines: 22877

💛 - Coveralls

@tracyboehrer tracyboehrer merged commit a0e84e9 into main Jan 24, 2024
13 checks passed
@tracyboehrer tracyboehrer deleted the southworks/fix/recognizer-text-number-old-version branch January 24, 2024 14:42
tracyboehrer pushed a commit that referenced this pull request Jan 24, 2024
…nstall scripts (#4608)

* add recognizers-text-number resolution

* add scripts to remove old version of recognizers-text-number

* remove rimraf package
@andrewconnell
Copy link

andrewconnell commented Jan 29, 2024

By using Yarn in the post-install script, you're FORCING a dependency on anyone using your package must have Yarn installed.

WHY? Why not use NPM?

It's fine if you use Yarn in your dev & builds, but to force it on ALL consumers of the package? 👎👎

For example, if a user doesn't have Yarn installed, this breaks all builds of new Teams projects created with TTK (see my referenced bug above

@tracyboehrer
Copy link
Member

@andrewconnell Apologies. We'll take care of it.

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 this pull request may close these issues.

4 participants