Adding package lock file (#45)

[m-gagne]

Resolves Issue #45

• Adds package.lock.json to source control
• Follows other MSFT projects like Roslyn and CoreFX etc.

[EvanBoyle]

Doesn't this conflict with the yarn.lock? Yarn is a better tool than NPM (read deterministic) and I'd prefer to stick to it wherever possible.

…

On Jun 14, 2017 7:55 PM, "Marc Gagne" ***@***.***> wrote: Resolves Issue #45 <#45> - Adds package.lock.json to source control - Follows other MSFT projects like Roslyn and CoreFX etc. ------------------------------ You can view, comment on, or merge this pull request online at: #46 Commit Summary - Adding package lock file File Changes - *A* package-lock.json <https://github.com/EvanBoyle/AzSearch.js/pull/46/files#diff-0> (4564) Patch Links: - https://github.com/EvanBoyle/AzSearch.js/pull/46.patch - https://github.com/EvanBoyle/AzSearch.js/pull/46.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#46>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACb1U3AAiklOa2eC4covMXixIWA2pqXTks5sEB6cgaJpZM4N6OxX> .

[EvanBoyle]

Unless there is a reason to use npm lock rather than the yarl lock we're already using I think we should close this one.