CLInotes.md

• npm/npm#11446

  • how to best support containers
  • symlink stuff makes vagrant and docker envs rough
  • expectations for users in layered envs
  • deploying and marshallin exp is painful

• npm/npm#11443

  • user story on fiing issues that we have
  • already firstclass support for git, but it is very focused (install and version)
  • webhooks, template package based on a repo (fits better on newww)
  • streamlining the workflow
  • fork and patch docs, http://darcs.net/

• npm/npm#11437

  • less configuration
  • less shared information across packages
  • woudl be interested in looking at the npmrc where the package.json is
  • specifically do not want to share config across packages
  • monorepo pattern of development

• npm/npm#11426

  • this is getting handled by rebecca already!
  • gauge

• npm/npm#11315

  • just no. there will always be one locus.
  • npm repo, npm issues <- sends you somewhere

• npm/npm#9032

  • current underlying implementaiton is already really complicated
  • as user other than root, perms should be squashed to umask, with exception of stomping on executable bits
  • as root: use effecting user id, not root, and not nobody
  • the nobody user is to prevent potential damage if a script sets something as writeable
  • node-tar <-- really needs to be correct, is an isaac pet project
  • current behavior is probably not correct
  • featuer request or bug?
  • STORY AROUND WINDOWS PERMISSIONS

• npm/npm#8928

  • actually a bug

• npm/npm#8821

  • UX is a concern we won't be getting to until late 2016, but we're interested in exploring based on

• npm/npm#8808

  • capistrano like deployment
  • feels like a separate product

• npm/npm#11517

  • we are bound by the node module resolution algorithm (extremely unlikely to change)
  • maybe look at npm prune

• npm/npm#11491

  • docs need help
  • will probably implement

• npm/npm#10395

  • we want browser deps but this solution is too much
  • see #9354
  • https://github.com/npm/npm/labels/front-end

• npm/npm#8797

  • do not rely on _ attributes
  • tooling to know where a package came from
  • generally we close issues if you focus on methodology not what you are trying to do

• npm/npm#8791

  • can be treated as file globs

• npm/npm#8784

• npm/npm#8764

• npm/npm#8684

• npm/npm#8677

• npm/npm#8655