You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are using modlean for quite some time, unfortunately the latest release (1.2.6) started to break our docker builds/node api:
Error: Cannot find module 'semver'
at Function.Module._resolveFilename (module.js:326:15)
at Function.Module._load (module.js:277:25)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/opt/api/node_modules/loopback-boot/lib/executor.js:2:14)
at Module._compile (module.js:410:26)
at Module._extensions..js (module.js:417:10)
at Object.require.extensions.(anonymous function) [as .js] (/opt/api/node_modules/babel-core/lib/api/register/node.js:214:7)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
module.js:328
throw err;
This is because the semver safe pattern was added. Would it be feasible to add a CLI option for specifying a JSON list of patterns to exclude, for instance --ignore=keep_us.json, or even .modcleanignore?
That way we could keep a small ignore json in our repository.
The text was updated successfully, but these errors were encountered:
Hey,
we are using modlean for quite some time, unfortunately the latest release (1.2.6) started to break our docker builds/node api:
This is because the semver safe pattern was added. Would it be feasible to add a CLI option for specifying a JSON list of patterns to exclude, for instance
--ignore=keep_us.json
, or even.modcleanignore
?That way we could keep a small ignore json in our repository.
The text was updated successfully, but these errors were encountered: