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
Upgrade to lodash 3.x #128
Conversation
@@ -8,6 +8,7 @@ var vm = require('vm'); | |||
|
|||
describe('browser support', function() { | |||
this.timeout(60000); // 60s to give browserify enough time to finish | |||
sandbox.reset(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is wrong. It should be either before(sandbox.reset)
or beforeEach(sandbox.reset)
. I think beforeEach makes more sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, that's clearly wrong. I blame tap.
Releasing this fix will be tricky, as npmjs.org displays README from the last published version. After we release 1.x, we must release another 2.x version to get the right README displayed. |
@bajtos I fixed the |
Regarding a release, it looks like there are a couple unreleased changes on master.. if you do a 1.x release just before releasing them that would be awesome :-) |
Nevermind, my repo was out of date.. you released from master 8 hours ago. |
LGTM |
Replace single-function module with full lodash, which can be shared with other packages if installed in a parent module.
See strongloop/strongloop#213 for context. This is an interim solution so that loopback-workspace can benefit from this change without having to upgrade to loopback-boot 2.x.