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

Regression in fast-glob@3.2.0 #142

Open
anilanar opened this issue Feb 15, 2020 · 3 comments
Open

Regression in fast-glob@3.2.0 #142

anilanar opened this issue Feb 15, 2020 · 3 comments

Comments

@anilanar
Copy link

Just a friendly notification that due to a regression in fast-glob@3.2.0, globby broke too: mrmlnc/fast-glob#253

Downstream example: dotansimha/graphql-code-generator#3512

@therealpecus
Copy link

fast-glob updated to 3.2.2 but there is still a regression uncaught. I don't have much data, we tracked it in an upstream project: dennisreimann/uiengine#56

@mrmlnc
Copy link
Contributor

mrmlnc commented Mar 31, 2020

The problem has been fixed in fast-glob@3.2.1. You can reinstall your dependencies, or update the package-lock file or something for yarn env.

@therealpecus
Copy link

@mrmlnc this might be a bit more elusive. globby might be missing a test to cover cases that arise in upstream packages because with either fast-glob@3.2.1 or fast-glob@3.2.2 the problem persists.

Running globby test suite does not surface any issue with any of the fast-glob versions that break upstream and for which force-installing fast-glob@3.1.1 fixes the behaviour instead.

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

No branches or pull requests

3 participants