Pin njsscan dependencies
disposedtrolley opened this issue · 1 comments
disposedtrolley commented
The njsscan dependencies don't appear to be pinned to specific versions. This can cause changes in behaviour like the problem described in #99 without the user having explicitly updated to a new release.
ajinabraham commented
This is expected. since njsscan is also expected to be used as a library/dependency, we try to avoid strict pinning that may cause dependency conflicts.