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

refactor #24

Merged
merged 13 commits into from
Apr 8, 2019
Merged

refactor #24

merged 13 commits into from
Apr 8, 2019

Conversation

jonschlinkert
Copy link
Member

No description provided.

@paulmillr
Copy link
Member

paulmillr commented Apr 1, 2019

@jonschlinkert just a quick note. to-regex — which adds non-core functionality as far as I see — adds 0.3MB of deps. That's a lot, because without it there are 0 deps.

to-regex  │ 21          │ 0.30M

Any chance we could move braces.toRegex out to a new pkg? Or just add a quick README notice on usage — no need for a new pkg.

@jonschlinkert
Copy link
Member Author

which adds non-core functionality as far as I see

Are you saying we should drop regex support from braces? How much of the 300k is safe-regex (the library that checks for catastrophic backtracking to prevent DDoS)?

If this gets too complicated I'll have to plan time in the future to work on this.

@paulmillr
Copy link
Member

@jonschlinkert here's to-regex (it says 0.13MB but in the end it's 0.3MB)

┌─────────────────┬────────────┬───────┐
│ name            │ children   │ size  │
├─────────────────┼────────────┼───────┤
│ define-property │ 7          │ 0.11M │
├─────────────────┼────────────┼───────┤
│ extend-shallow  │ 4          │ 0.04M │
├─────────────────┼────────────┼───────┤
│ regex-not       │ 2          │ 0.02M │
├─────────────────┼────────────┼───────┤
│ safe-regex      │ 1          │ 0.02M │
├─────────────────┼────────────┼───────┤
│ 4 modules       │ 9 children │ 0.13M │
└─────────────────┴────────────┴───────┘

@paulmillr
Copy link
Member

@jonschlinkert as far as I see from the readme there's no support for regex api in the stable version of braces. So, in this case, i'd argue for keeping the api just as simple; and adding a readme notice on how to convert to RegExps.

@paulmillr
Copy link
Member

YAY! 🌈

Any ETA on the release?

@jonschlinkert
Copy link
Member Author

Any ETA on the release?

it's done. I just need to wrap it up and release. probably today

@paulmillr
Copy link
Member

Great to see one less tool (appveyor).

@jonschlinkert
Copy link
Member Author

@paulmillr FWIW I use a tool to generate documentation, the badges are in a template, so they'll automatically be updated. The appveyor badge is excluded if there is no .appveyor.yml file.

@paulmillr
Copy link
Member

@jonschlinkert ping!

@jonschlinkert
Copy link
Member Author

What are you pinging about @paulmillr?

@paulmillr
Copy link
Member

Let's release it 😃

@jonschlinkert
Copy link
Member Author

Let's release it 😃

Are you volunteering to do the docs and changelog? :)

@paulmillr
Copy link
Member

Working on anymatch & chokidar updates right now.

@paulmillr
Copy link
Member

I’ve prepared new builds — Chokidar is 1/8th of previous size and feels super lean now. Can’t wait on getting these packages released!

@jonschlinkert
Copy link
Member Author

Can’t wait on getting these packages released!

I'll be working on it this weekend.

@jonschlinkert jonschlinkert merged commit bb5b5ba into master Apr 8, 2019
@jonschlinkert jonschlinkert deleted the dev branch April 8, 2019 22:42
@jonschlinkert
Copy link
Member Author

@paulmillr how's everything working out?

@paulmillr
Copy link
Member

@jonschlinkert it’s awesome, we’re fixing tests across platforms and waiting for node 8.16

@jonschlinkert
Copy link
Member Author

we’re fixing tests across platforms and waiting for node 8.16

I hope I didn't break anything!

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.

None yet

2 participants