issues
search
defunctzombie
/
package-browser-field-spec
Spec document for the 'browser' field in package.json
437
stars
20
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Threat browser field as mandatory for non server-only packages
#18
bitifet
opened
8 months ago
9
node --eval "fs.writeFileSync('.prettierrc','{}\n')"
#17
mathieubathalon
closed
1 year ago
1
declare alternative main and ignore dependencies at the same time ?
#16
cancerberoSgx
opened
6 years ago
1
Fix a broken link to "browser" property
#15
ranyitz
closed
3 years ago
1
typo: inappropriate
#14
marwahaha
closed
3 years ago
0
relative path will resolve module of same name
#13
louisbuchbinder
opened
7 years ago
0
javascript -> JavaScript
#12
bennycode
opened
7 years ago
0
resolve files inside subfolder as if in root
#11
AlmirKadric
opened
7 years ago
0
Replace main and specific files together
#10
alexleonescalera
opened
7 years ago
1
Adopt a more generic approach?
#9
rauschma
opened
7 years ago
5
[RFC] Discuss WASM, WASM Fallback package resolution support
#8
TheLarkInn
opened
7 years ago
2
Add "Status" section to track which tools support this spec
#7
broofa
closed
5 years ago
0
feature: resolve main reference to other modules
#6
pemrouz
opened
8 years ago
0
How to handle paths outside of package.json's directory
#5
mk-pmb
opened
8 years ago
0
Ignored packages: Benefits of empty object over false?
#4
mk-pmb
opened
8 years ago
0
How ignored modules shall behave when imported from outside
#3
yurydelendik
opened
8 years ago
0
Impossible to implement safely with deduplicated dependencies?
#2
joepie91
opened
8 years ago
1
Remove mention of ws
#1
rstacruz
closed
8 years ago
0