mozilla/npm-lockdown issues and pull requests

#60 - Add Mozilla Code of Conduct

Pull Request - State: closed - Opened by Mozilla-GitHub-Standards almost 6 years ago

#59 - CODE_OF_CONDUCT.md file missing

Issue - State: closed - Opened by Mozilla-GitHub-Standards almost 6 years ago

#57 - New RSS with also me working with Google on a blnew internet protocol with diriivative works

Issue - State: closed - Opened by MICKHAILx over 8 years ago - 1 comment

#56 - add yarnpkg to related tools

Pull Request - State: closed - Opened by graingert over 8 years ago

#55 - Use .gitattributes to insure bins can be run. Fixes #42. v0.0.10-dev

Pull Request - State: open - Opened by rektide over 8 years ago

#54 - Dependencies are deprecated in 0.0.8-dev

Issue - State: open - Opened by anatomic over 8 years ago - 1 comment

#53 - (solved) How to get npm-lockdown running on CircleCI

Issue - State: open - Opened by hakunin over 8 years ago

#52 - Warning: no shasum for ...

Issue - State: open - Opened by reggi almost 9 years ago

#51 - Fix link to npm shrinkwrap

Pull Request - State: closed - Opened by z38 almost 9 years ago - 1 comment

#50 - Use https

Pull Request - State: closed - Opened by jackwanders almost 9 years ago

#49 - Error with the hook

Issue - State: open - Opened by nikolay almost 9 years ago - 1 comment

#48 - Error: spawn ENOENT

Issue - State: open - Opened by tylercollier about 9 years ago - 7 comments

#47 - I get a JSON file error all the time

Issue - State: closed - Opened by cesarvega about 9 years ago - 1 comment

#46 - Error during lockdown-relock for a large set of deps

Issue - State: closed - Opened by pmclanahan over 9 years ago - 4 comments

#45 - Use npm, not process environment, to determine registry before starting server

Pull Request - State: closed - Opened by jackwanders over 9 years ago

#44 - Error recovering .cache.json for namespaced modules

Issue - State: open - Opened by ddalmais over 9 years ago - 3 comments

#43 - "glob error" code: 'EMFILE', I think due to a very large dependency tree

Issue - State: open - Opened by rjmunro over 9 years ago - 1 comment

#42 - v0.0.8-dev has wrong line endings for lockdown-relock file

Issue - State: open - Opened by rjmunro over 9 years ago - 19 comments

#41 - publish 0.0.8 on npm

Issue - State: closed - Opened by vladikoff over 9 years ago - 3 comments

#40 - RangeError: Maximum call stack size exceeded

Issue - State: closed - Opened by earnubs over 9 years ago - 3 comments

#39 - Error when running lockdown-relock if some npm modules are installed from git

Issue - State: open - Opened by muffinresearch almost 10 years ago - 6 comments

#38 - Update documentation about force publish

Pull Request - State: closed - Opened by indexzero almost 10 years ago - 1 comment

#37 - Cannot read property 'dist' of undefined

Issue - State: open - Opened by lazywei almost 10 years ago - 1 comment

#36 - Cannot complete node_modules/.bin/lockdown-relock command. RangeError

Issue - State: closed - Opened by alexleone almost 10 years ago - 1 comment

#35 - Fixing cache problems

Pull Request - State: closed - Opened by nuxlli almost 10 years ago - 2 comments

#34 - "npm install" with {"preinstall": "lockdown"} on Windows

Issue - State: closed - Opened by andreicristianpetcu about 10 years ago - 3 comments

#33 - Adding license file and license info to package.json

Pull Request - State: closed - Opened by pdehaan about 10 years ago - 2 comments

#32 - Please add a LICENSE file

Issue - State: closed - Opened by andreicristianpetcu about 10 years ago - 1 comment

#31 - RangeError: Maximum call stack size exceeded

Issue - State: closed - Opened by andreicristianpetcu about 10 years ago - 10 comments

#30 - Load npm config for registry details.

Pull Request - State: closed - Opened by tomgco over 10 years ago - 3 comments

#29 - npm >= 1.4.11 (i.e., nodejs >= 0.10.29) will break npm-lockdown

Issue - State: closed - Opened by jrgm over 10 years ago - 8 comments

#28 - Fix typo in warning message.

Pull Request - State: closed - Opened by dpogue over 10 years ago - 1 comment

#27 - Functionality Questionable - Didn't work as intended

Issue - State: open - Opened by crh3675 over 10 years ago - 3 comments

#26 - add the ability to specify which npm mirror to fetch resources from

Pull Request - State: closed - Opened by shane-tomlinson about 11 years ago - 1 comment

#25 - setup gitmirror at mozilla

Issue - State: open - Opened by seanmonstar over 11 years ago

#24 - copy the previous ENV to the new ENV

Pull Request - State: closed - Opened by seanmonstar over 11 years ago - 1 comment

#23 - add HOME var to spawned sub-processes, required for lockdown to function...

Pull Request - State: closed - Opened by lloyd over 11 years ago - 1 comment

#22 - lockdown fails on node v0.10.x when node-gyp is in play

Issue - State: closed - Opened by lloyd over 11 years ago - 1 comment

#21 - explicitly pass environment variables to child npm install - fixes lockd...

Pull Request - State: closed - Opened by lloyd over 11 years ago

#20 - lockdown script not running under travis

Issue - State: closed - Opened by lloyd over 11 years ago - 1 comment

#19 - Improve readability for ongoing usage of lockdown

Pull Request - State: closed - Opened by ozten about 12 years ago - 1 comment

#18 - Hard-code the temp directory for nix

Pull Request - State: closed - Opened by zaach over 12 years ago

#17 - lockdown behavior varies by user

Issue - State: open - Opened by ozten over 12 years ago

#16 - lockdown bumps minimal required node version to 0.6.17

Issue - State: closed - Opened by ozten over 12 years ago - 2 comments

#15 - Revert temp directory to unix value. It doesn't seem to be used by windows

Pull Request - State: closed - Opened by zaach over 12 years ago - 5 comments

#14 - "npm install" output is printed twice

Issue - State: open - Opened by zaach over 12 years ago - 2 comments
Labels: bug

#13 - Use npm's logic for finding the home directory on Windows

Pull Request - State: closed - Opened by zaach over 12 years ago - 2 comments

#12 - improve developer experience for updating dependencies

Issue - State: open - Opened by lloyd over 12 years ago - 1 comment
Labels: enhancement

#11 - finds cache from npm module

Pull Request - State: closed - Opened by seanmonstar over 12 years ago - 1 comment

#10 - don't copy .bin/lockdown

Pull Request - State: closed - Opened by seanmonstar over 12 years ago

#9 - use a copy of process.env

Pull Request - State: closed - Opened by seanmonstar over 12 years ago

#8 - Why must preinstall be copied into directory?

Issue - State: closed - Opened by seanmonstar over 12 years ago

#7 - npm cache doesn't always have the needed shasums

Issue - State: open - Opened by seanmonstar over 12 years ago - 4 comments

#6 - cache directory is wrong on Windows

Issue - State: closed - Opened by seanmonstar over 12 years ago

#5 - console colors are lost

Issue - State: open - Opened by seanmonstar over 12 years ago - 1 comment
Labels: bug

#4 - tests

Issue - State: open - Opened by lloyd over 12 years ago

#3 - document caveats

Issue - State: open - Opened by lloyd over 12 years ago

#2 - why not shrinkwrap? why not seal?

Issue - State: closed - Opened by lloyd over 12 years ago

#1 - document how it works

Issue - State: open - Opened by lloyd over 12 years ago - 2 comments

GitHub / mozilla/npm-lockdown issues and pull requests