-
Notifications
You must be signed in to change notification settings - Fork 47
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
remove lodash
dependency
#40
Labels
Comments
Closed
fulls1z3
changed the title
[enhancement] remove lodash dependency
[enhancement] remove May 9, 2017
lodash
dependency
fulls1z3
pushed a commit
that referenced
this issue
May 9, 2017
fulls1z3
pushed a commit
that referenced
this issue
May 9, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
pushed a commit
that referenced
this issue
Sep 4, 2017
fulls1z3
changed the title
[enhancement] remove
remove Sep 16, 2017
lodash
dependencylodash
dependency
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ... (check one with "x")
Current behavior
lodash
offers great functionality as well as several errors causing a lot of effort to solve - especially with types (#38). Furthermore, it increases the bundle size (50KB~500KB).Expected/desired behavior
Get rid of
lodash
, do not depend on it!Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Language: [all | TypeScript X.X | ES6/7 | ES5]
Node (for AoT issues):
node --version
=The text was updated successfully, but these errors were encountered: