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

feat: move from braces to brace-expansion #1302

Closed
wants to merge 1 commit into from

Conversation

43081j
Copy link
Contributor

@43081j 43081j commented Feb 4, 2024

This replaces braces with brace-expansion, a much leaner and more actively maintained package.

This replaces `braces` with `brace-expansion`, a much leaner and more
actively maintained package.
@paulmillr
Copy link
Owner

What's there to maintain? It's probably much slower.

@43081j
Copy link
Contributor Author

43081j commented Feb 5, 2024

happy to find out if you like! i'll have a look this evening if i can

the leanness is more the reason to move. i do agree there's not much to maintain once this works, other than any security updates, etc.

@paulmillr
Copy link
Owner

Leanness is:

  1. Rewrite chokidar to drop globbing, decreasing amount of deps to a few.
  2. Switch to typescript.

Started in #1195, but never finished.

@43081j
Copy link
Contributor Author

43081j commented Feb 5, 2024

do you want any help?

braces is small fish but still responsible for dependency bloat either way. if we can solve that by dropping globbing altogether though, i'm happy to go in whatever direction it is you want

you were right though, brace-expansion in particular is slightly slower than braces. so i'll go open a PR in brace-expansion to fix that whether we use it here or not 👍

@paulmillr
Copy link
Owner

Yes, if anyone can help on the rewrite, it would be highly appreciated. Non-trivial task.

@43081j
Copy link
Contributor Author

43081j commented Feb 5, 2024

sure no worries, i'll take a look at it. non trivial esm/ts conversions are my kind of thing 👀

@43081j
Copy link
Contributor Author

43081j commented Feb 5, 2024

for anyone curious, i've opened a perf fix in juliangruber/brace-expansion#64 which makes it out-perform braces by a fair amount

@paulmillr paulmillr force-pushed the master branch 2 times, most recently from 368cb02 to 7c50e25 Compare February 6, 2024 22:52
@hellobontempo
Copy link

hellobontempo commented Jun 28, 2024

Hi there! I came across this PR while looking to see if there was chatter about upgrading braces to 3.0.3 because of this security vulnerability: https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727

Happy to file a separate issue if that's preferred!

@paulmillr
Copy link
Owner

@hellobontempo learn how version ranges work

@paulmillr paulmillr closed this Jun 29, 2024
@hellobontempo
Copy link

@paulmillr - I missed the tilda when I skimmed the package. No need to be rude. Have a great day!

@paulmillr
Copy link
Owner

@hellobontempo you can tell this to other 10 people who've opened same pull requests https://github.com/paulmillr/chokidar/pulls?q=is%3Apr+is%3Aclosed

@j-crowe
Copy link

j-crowe commented Jul 1, 2024

@paulmillr learn how to educate people respectfully. Kindness and respect are fundamental skills. Do better.

@43081j
Copy link
Contributor Author

43081j commented Jul 1, 2024

@j-crowe i don't think this is constructive. paul's messages aren't so helpful either, i understand, but hes been dealing with the burden of a lot of these issues lately so it is understandable

if you can solve the problem with version ranges, please do share what you used in the end so others can do the same

meanwhile, v4 is being worked on which will drop the dependency

@paulmillr
Copy link
Owner

@j-crowe kindness, respect and documentation updates wouldn't help me to not get another 10 pull requests replacing ~3.0.2 with ~3.0.3. Everyone would keep doing this because people are convinced automatic NPM dependency scanners are good. They are not: they are mostly evil.

@j-crowe
Copy link

j-crowe commented Jul 1, 2024

@43081j nothing that was said warranted the response from @paulmillr. These responses, especially from an author, taint projects and communities supporting them.

@paulmillr I understand the frustration, but you can still educate people respectfully. Hostile comments only reflect poorly on your own character and the projects you're dedicating yourself to.

Good luck. I appreciate your contributions.

@paulmillr
Copy link
Owner

@j-crowe there is no support from community. No one wants to touch it. Sometimes contributors like @43081j come. That's it. It's a lot of unpaid work just to get another dozen of issues from users who don't know what they're doing.

Repository owner locked as resolved and limited conversation to collaborators Jul 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants