Giters
browserify
/
resolve
Implements the node.js require.resolve() algorithm
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
772
Watchers:
16
Issues:
162
Forks:
181
browserify/resolve Issues
Critical Vulnerability with monorepo-symlink-test
Closed
9 months ago
Comments count
8
Any reason to publish /test?
Closed
7 months ago
Comments count
5
The test/resolver/malformed_package_json/package.json leads to an fatal error when starting meteor
Closed
8 months ago
Comments count
39
Package includes test folder
Closed
8 months ago
Comments count
1
`npx resolve` errors
Closed
9 months ago
Comments count
17
monorepo-symlink-test security issue
Closed
9 months ago
Comments count
1
Critical Vulnerability reported on monorepo-symlink-test - False Negative
Closed
9 months ago
Comments count
1
Incorrect work on Linux (`Error: `resolve` must be run directly as an executable`)
Closed
9 months ago
[Security] Malicious code in `test/resolver/multirepo`
Closed
9 months ago
Comments count
19
monorepo-symlink-test
Closed
9 months ago
Comments count
5
Used monorepo-symlink-test is malicious
Closed
9 months ago
Comments count
1
Critical vulnerability monorepo-symlink-test
Closed
9 months ago
Comments count
2
Critical Vulnerability due to Resolve Package -- monorepo-symlink-test
Closed
9 months ago
Comments count
2
Error "ENOENT: no such file or directory, open '../../is-core-module/core.json"
Closed
10 months ago
Comments count
20
This package is being flagged as malware - false positive
Closed
a year ago
Comments count
1
The 'test' directory seems to contain the code of malicious package 'monorepo-symlink-test'
Closed
a year ago
Comments count
1
Resolve monorepo-symlink-test vulnerable package
Closed
a year ago
Comments count
1
monorepo-symlink-test GHSA-2jcg-qqmg-46q6 Vulnerability
Closed
a year ago
Comments count
9
Remove readFileSync
Closed
a year ago
Comments count
1
WebpackError: TypeError: Unable to determine current node version
Closed
a year ago
Question: NPM version 1.22.3 is published but 1.22.2 is marked as `latest`
Closed
a year ago
Comments count
1
Result differs from Node's require.resolve when using `basedir` option with symlinks
Updated
a year ago
Comments count
9
Unexpected end of input, expected the token `}`
Closed
a year ago
Comments count
3
Please make async resolve mockable with pure sinon
Closed
a year ago
Comments count
1
Unable to resolve a package by its own name
Updated
2 years ago
Comments count
2
Question around dummy packages in monorepo test
Closed
2 years ago
Comments count
3
Remove npm package monorepo-symlink-test (contains malicious code)
Closed
2 years ago
Comments count
1
Reference to malicious package monorepo-symlink-test causing security scan to fail
Closed
2 years ago
Comments count
4
resolve result is inconsistent with require.resolve if windows virtual drive is used
Closed
2 years ago
Comments count
9
v1.22.1 patch request
Closed
2 years ago
Comments count
3
Exclude non-essential files from published package (especially test/**)
Closed
2 years ago
Comments count
15
Consider excluding test code from the npm package
Closed
2 years ago
Comments count
2
Improvement idea - globally configurable helper functions
Updated
2 years ago
Comments count
3
`pathFilter` (or some new API) should support implementations of `exports`
Closed
2 years ago
Comments count
11
custom path module
Updated
2 years ago
Comments count
15
SyntaxError: Unexpected end of JSON input
Closed
2 years ago
Comments count
5
intentionally malformed package.json fixture in tests breaks flowtype when checking node_modules
Closed
2 years ago
Comments count
9
Fix non-valid values in .editorconfig file
Closed
2 years ago
Comments count
1
v1.21.0 breaks with next.js, or without graceful-fs upgrade
Closed
2 years ago
Comments count
23
Intentionally malformed package.json causing build errors with meteor
Closed
2 years ago
Comments count
4
Error with incorrectly closed json
Closed
2 years ago
Comments count
1
Prioritize moduleDirectory array elements
Closed
2 years ago
Comments count
1
not support absolute path?
Closed
2 years ago
Comments count
5
Dependency package "path-parse - 1.0.6" is reported as vulnerable by Whitesource scan
Closed
3 years ago
Comments count
1
Use throwIfNoEntry for default isFile and isDirectory
Closed
3 years ago
Comments count
4
Support browser filed
Closed
3 years ago
Comments count
1
Version update
Closed
3 years ago
Comments count
1
Multi level "exports" not supported?
Closed
3 years ago
Comments count
4
how to get a version in node .js of a package?
Closed
3 years ago
Comments count
1
path-parse vulnerability
Closed
3 years ago
Comments count
1
Previous
Next