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

Use yarn #24

Merged
merged 2 commits into from
Jan 19, 2022
Merged

Use yarn #24

merged 2 commits into from
Jan 19, 2022

Conversation

walaszczykm
Copy link
Collaborator

Type of change

  • Docs
  • Bug fix
  • Feature

Packages

  • @livechat/widget-core
  • @livechat/widget-react
  • @livechat/widget-vue
  • @livechat/widget-angular

Issue

N/A

Description

Switch used package manager from npm to yarn mainly because of workspaces bootstrapping issues. It turned out that npm is always trying to resolve all dependencies first on its registry without taking into consideration which packages come from workspaces. Although after this process it successfully resolves them and links properly. Unfortunately at this first stage if in the monorepo we have not yet published version it makes npm install fail without even trying to resolve local packages. On the other hand yarn does not have this issue when used for projects with workspaces.

Additionally, upgrade angular package dev dependencies to the latest minor to support TypeScript >= 4.50 which is used in all other places in the mono repo.

@walaszczykm walaszczykm added the enhancement New feature or request label Jan 19, 2022
@walaszczykm walaszczykm requested a review from a team as a code owner January 19, 2022 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant