you don't know
hi my name is @ag_dubs
?????lolwat
if you don't understand how npm works
if you don't understand how npm works
that's my problem
if you don't understand how npm works
that's my problem
stuff not everyone knows
create a package.json
npm init
knows your deps from node_modules
knows your repository from git repo
always adds keys, never deletes
create a package.json with defaults
npm init --yes
add deps from the CLI
npm i --save
npm i --save-dev
add deps from the CLI
npm i -S
npm i -D
npm... global cache?
.npm/
modules are stored in the home directory
... but you can't use this offline because it still hits the network
npm install offline
npm install --cache-min 999999
we should probably just alias this to:
npm install --offline
lock down your deps
npm shrinkwrap
we believe in semver
run scripts
npm test
npm start
npm run $anything
Automate CLI workflows, e.g. build steps, migrations
lifecycle events
publish, install, uninstall, version, test, stop, start, restart
pre, post
run scripts are composable
"db:migrate": "knex migrate:latest"
"db:seed": "knex seed:run"
"db:reset": "npm run db:migrate && npm run db:seed"
scoped packages
npm i @scope/name
scoped packages
npm i @scope/name
scoped packages are private by default but you can make them public:
npm publish --access=public
npm private modules
npm private modules
(it's recursive! get it? get it?)
npm private modules
(it's recursive! get it? get it?)
npmnpmnpmnpmnpmnpmlolololololol
private modules
npm init --scope=<usrname>
Use your private modules side by side with modules from the public registry
Managing access is hard...
npm organizations
npm team
create teams and add members
grant and revoke access to packages via scopes
npm on-site
run your own on-premises npm registry
npm login
--registry=http://reg.amazing.com
npm on-site
run your own on-premises npm registry
npm login
--registry=http://reg.amazing.com
(get it? run? runner?)
thanks!
me => @ag_dubs
bit.ly/you-dont-know-npm