issues
search
browserify
/
browser-resolve
resolve function which support the browser field in package.json
MIT License
102
stars
70
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Pass through original `opts` properties to resolve
#52
jmm
closed
9 years ago
1
Make browser field adjust incoming "deep" module references.
#51
justinbmeyer
closed
9 years ago
17
Upgraded resolve and added support for basedir
#50
securingsincity
closed
9 years ago
3
Fixed an incorrect reference to pkg_path
#49
f5io
closed
9 years ago
0
Implement synchronous api
#48
wilsonjackson
closed
9 years ago
1
Synchronous version?
#47
wilsonjackson
closed
9 years ago
1
Breakage when a browser shim file does not exist
#46
atrigent
closed
9 years ago
1
npm install failing
#45
morganherlocker
closed
10 years ago
1
Allow Windows nodejs to search <drive>:\node_modules
#44
roncli
closed
10 years ago
3
package: update "resolve" to v0.7.1
#43
TooTallNate
closed
10 years ago
0
support recursivity in paths option
#42
slorber
closed
10 years ago
2
Using the paths option, doesn't lookup anymore on node_modules
#41
slorber
closed
10 years ago
4
Issue 37
#40
JamesKyburz
closed
10 years ago
1
Bump upgrade resolve to fix browserify hanging bug
#39
airportyh
closed
10 years ago
1
Fixes Issue 37
#38
JamesKyburz
closed
10 years ago
3
Fails when package.json main string doesn't match browser source file
#37
JamesKyburz
closed
10 years ago
2
"os" module
#36
ljharb
closed
10 years ago
3
call the packageFilter() with the pkgdir
#35
ghost
closed
10 years ago
0
Synchronous API
#34
tarruda
closed
10 years ago
2
Upgrade resolve to 0.6.1
#33
gre
closed
10 years ago
5
purpose of empty.js
#32
juliangruber
closed
10 years ago
3
Update resolve to 0.5.1
#31
ForbesLindesay
closed
11 years ago
0
Permit engine shims to be overridden
#30
kriskowal
closed
11 years ago
8
support module replacement outside current module
#29
terinjokes
closed
10 years ago
10
wrong comment line
#28
yuri-karadzhov
closed
11 years ago
2
resolving with pkg metadata breaks browserify
#27
thlorenz
closed
11 years ago
9
Resolving with package metadata and improve legacy browserify field check.
#26
jaredhanson
closed
11 years ago
1
Pass 'extensions' key down to node-resolve call
#25
andreypopp
closed
11 years ago
0
Add support for `opts.package`, and correctly handle browserify transform.
#24
jaredhanson
closed
11 years ago
2
Allow browser replacement with directory and pass package option through.
#23
jaredhanson
closed
11 years ago
21
ignore and map options?
#22
curvedmark
closed
11 years ago
1
Include file path in error message
#21
timoxley
closed
11 years ago
0
options passed to resolve
#20
mikerobe
closed
11 years ago
14
don't require explicit file extension
#19
mahnunchik
closed
11 years ago
18
Support browserify field as well as browser field for legacy reasons
#18
Raynos
closed
11 years ago
0
Chrome App sockets
#17
amiuhle
closed
11 years ago
7
updated querystring
#16
juliangruber
closed
11 years ago
17
Update to streams 2 api
#15
juliangruber
closed
11 years ago
1
support `false` as a browser field value, added examples
#14
ghost
closed
11 years ago
1
wrong paths used
#13
juliangruber
closed
11 years ago
4
Pass extensions key through parent argument
#12
andreypopp
closed
11 years ago
24
dgram shim
#11
ghost
closed
11 years ago
0
Support resolving when local path has no extension
#10
rudyjahchan
closed
11 years ago
4
node0.6.x compatibility fix
#9
thlorenz
closed
11 years ago
0
Set correct scheme if https module is used.
#8
tonistiigi
closed
11 years ago
2
`constants` builtin is missing
#7
chrisdickinson
closed
11 years ago
2
extract node buildins
#6
sokra
closed
11 years ago
18
events.EventEmitter.removeAllListeners removes no listeners if no arguments are passed
#5
segrey
closed
11 years ago
0
update all builtins to match latest 0.8
#4
Raynos
closed
11 years ago
4
require('utils') + JSON.parse
#3
Raynos
closed
11 years ago
1
Previous
Next