issues
search
voorhoede
/
npm-style-guide
Opinionated npm Style Guide for teams.
https://github.com/voorhoede/npm-style-guide#readme
Creative Commons Zero v1.0 Universal
91
stars
11
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
add badge
#24
jbmoelker
closed
8 years ago
0
add CC0 1.0 Universal license
#23
jbmoelker
closed
8 years ago
0
Prefix run tasks
#22
sveisvei
closed
8 years ago
0
Prefix tasks with group is only convention
#21
sveisvei
closed
8 years ago
2
list all standard scripts + example package.json + rephrasing
#20
jbmoelker
closed
8 years ago
0
fix ToC links, rule order, whitespace and typos
#19
jbmoelker
closed
8 years ago
0
update "Prefix tasks" with simpler example
#18
jbmoelker
closed
8 years ago
0
Add "Customise initial package.json" guideline?
#17
jbmoelker
opened
8 years ago
1
feat(document-api): add rule about documenting api
#16
jpsc
closed
8 years ago
0
feat(specify-engines): add rule about engines
#15
jpsc
closed
8 years ago
0
feat(rule): add "Avoid shorthand command flags" rule
#14
jbmoelker
closed
8 years ago
1
Add "Document your script API" guideline?
#13
jbmoelker
closed
8 years ago
1
Consistently write *npm* in lowercase.
#12
jbmoelker
closed
8 years ago
1
Prefix tasks
#11
petergoes
closed
8 years ago
4
feat(script-names): use standard script names
#10
jpsc
closed
8 years ago
1
Policy: Approve PRs before merging?
#9
jbmoelker
closed
8 years ago
1
style-guide badge
#8
petergoes
opened
8 years ago
3
use standard script names
#7
jpsc
closed
8 years ago
1
prefix tasks to bundle them
#6
jpsc
closed
8 years ago
3
feat(rule): add global modules rules
#5
jpsc
closed
8 years ago
0
specify engines on package.json ?
#4
jpsc
closed
8 years ago
8
use `NODE_ENV` for conditionaly run tasks?
#3
jpsc
opened
8 years ago
1
feat(rule): add atomic scripts definition
#2
jpsc
closed
8 years ago
0
feat(rule): add rule about system agnostic tasks
#1
jpsc
closed
8 years ago
0