You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New packages add husky hooks to the git repository.
Desired Behavior
Provide an optional flag to disable husky
Suggested Solution
tsdx create something-in-monorepo --no-hooks
Who does this impact? Who is this for?
This is for developers maintaining mono repos containing multiple packages. New hooks shouldn't be added when packages are created.
This is especially troublesome when switching between feature-branches where each branch might not have the same packages. The hooks fail and prevent committing, pushing, etc.
Describe alternatives you've considered
The alternative is to not use tsdx to create the new packages but to manually copy and paste existing packages in the monorepo.
Or I could manually open the commit hook files and delete the generated code
Additional context
We're using tsdx for some packages stored in the tinacms monorepo, which is managed using lerna.
The text was updated successfully, but these errors were encountered:
Current Behavior
New packages add husky hooks to the git repository.
Desired Behavior
Provide an optional flag to disable husky
Suggested Solution
Who does this impact? Who is this for?
This is for developers maintaining mono repos containing multiple packages. New hooks shouldn't be added when packages are created.
This is especially troublesome when switching between feature-branches where each branch might not have the same packages. The hooks fail and prevent committing, pushing, etc.
Describe alternatives you've considered
The alternative is to not use tsdx to create the new packages but to manually copy and paste existing packages in the monorepo.
Or I could manually open the commit hook files and delete the generated code
Additional context
We're using
tsdx
for some packages stored in thetinacms
monorepo, which is managed usinglerna
.The text was updated successfully, but these errors were encountered: