GitHub / browserify/resolve issues and pull requests
#333 - Configure Renovate
Pull Request -
State: open - Opened by renovate[bot] about 1 month ago
- 1 comment
#332 - [Tests] fix posttest script on Windows
Pull Request -
State: closed - Opened by targos 7 months ago
- 7 comments
#331 - Tests fail to run on Windows
Issue -
State: closed - Opened by targos 7 months ago
- 2 comments
#330 - Configure Renovate
Pull Request -
State: closed - Opened by BridgeAR 7 months ago
- 1 comment
#329 - 1.22.9 includes test/list-exports, reintroducing (false) malicious code flag
Issue -
State: closed - Opened by TomiTakussaari 7 months ago
- 3 comments
#327 - Node.js imports field is not supported
Issue -
State: open - Opened by pcdevil 8 months ago
- 3 comments
#326 - Provide canonical resolution resource for malicious code flag
Issue -
State: closed - Opened by duncanhall 11 months ago
- 5 comments
#325 - [Chore] Cleanup npm package
Pull Request -
State: closed - Opened by yhnavein 12 months ago
- 1 comment
#324 - [meta] ship only production files
Pull Request -
State: closed - Opened by osher about 1 year ago
- 8 comments
#323 - Any reason to publish /test?
Issue -
State: closed - Opened by vvscode over 1 year ago
- 5 comments
#322 - Package includes test folder
Issue -
State: closed - Opened by johnlister almost 2 years ago
- 4 comments
#321 - [spam]
Pull Request -
State: closed - Opened by sloops77 almost 2 years ago
#320 - add support for package.json exports
Pull Request -
State: open - Opened by isaacs almost 2 years ago
- 3 comments
#319 - monorepo-symlink-test security issue
Issue -
State: closed - Opened by avosper-intellaegis almost 2 years ago
- 1 comment
#318 - Critical Vulnerability with monorepo-symlink-test
Issue -
State: closed - Opened by bbuck almost 2 years ago
- 8 comments
#317 - Critical Vulnerability reported on monorepo-symlink-test - False Negative
Issue -
State: closed - Opened by bzemms almost 2 years ago
- 1 comment
#316 - Incorrect work on Linux (`Error: `resolve` must be run directly as an executable`)
Issue -
State: closed - Opened by vvscode almost 2 years ago
#315 - `npx resolve` errors
Issue -
State: closed - Opened by vvscode almost 2 years ago
- 17 comments
#314 - Used monorepo-symlink-test is malicious
Issue -
State: closed - Opened by ThomazPom almost 2 years ago
- 1 comment
#313 - change package name on test to avoid scanning issue
Pull Request -
State: closed - Opened by cichelero almost 2 years ago
- 4 comments
#312 - monorepo-symlink-test
Issue -
State: closed - Opened by roberthockley almost 2 years ago
- 5 comments
#311 - Critical vulnerability monorepo-symlink-test
Issue -
State: closed - Opened by Iuriy-Budnikov almost 2 years ago
- 2 comments
#310 - Critical Vulnerability due to Resolve Package -- monorepo-symlink-test
Issue -
State: closed - Opened by kjcohen almost 2 years ago
- 2 comments
#309 - [Security] Malicious code in `test/resolver/multirepo`
Issue -
State: closed - Opened by aashutoshrathi almost 2 years ago
- 19 comments
#308 - Remove tests from npm package
Pull Request -
State: closed - Opened by boidolr almost 2 years ago
- 1 comment
#306 - This package is being flagged as malware - false positive
Issue -
State: closed - Opened by chiahrens about 2 years ago
- 1 comment
#305 - The 'test' directory seems to contain the code of malicious package 'monorepo-symlink-test'
Issue -
State: closed - Opened by lanzkron about 2 years ago
- 1 comment
#304 - Resolve monorepo-symlink-test vulnerable package
Issue -
State: closed - Opened by frabbiDAndT about 2 years ago
- 1 comment
#303 - monorepo-symlink-test GHSA-2jcg-qqmg-46q6 Vulnerability
Issue -
State: closed - Opened by castafab about 2 years ago
- 9 comments
#302 - Remove readFileSync
Issue -
State: closed - Opened by polRk about 2 years ago
- 1 comment
#301 - WebpackError: TypeError: Unable to determine current node version
Issue -
State: closed - Opened by sherlockfeng about 2 years ago
#300 - Treat missing "main" as index.js
Pull Request -
State: closed - Opened by rotu about 2 years ago
- 1 comment
#299 - Fix invalid values in editorconfig
Pull Request -
State: closed - Opened by dpuscher about 2 years ago
#298 - Question: NPM version 1.22.3 is published but 1.22.2 is marked as `latest`
Issue -
State: closed - Opened by akphi over 2 years ago
- 1 comment
#297 - Error "ENOENT: no such file or directory, open '../../is-core-module/core.json"
Issue -
State: closed - Opened by SuperOleg39 over 2 years ago
- 20 comments
#296 - [meta] Exclude tests and config files from publish
Pull Request -
State: closed - Opened by dosisod over 2 years ago
- 1 comment
#295 - Result differs from Node's require.resolve when using `basedir` option with symlinks
Issue -
State: open - Opened by j-christoffersen over 2 years ago
- 9 comments
#294 - Unexpected end of input, expected the token `}`
Issue -
State: closed - Opened by AndyFang36 over 2 years ago
- 3 comments
#293 - Please make async resolve mockable with pure sinon
Issue -
State: closed - Opened by art-alexeyenko over 2 years ago
- 1 comment
#292 - Question around dummy packages in monorepo test
Issue -
State: closed - Opened by plygrnd almost 3 years ago
- 3 comments
#291 - Remove npm package monorepo-symlink-test (contains malicious code)
Issue -
State: closed - Opened by muhanator almost 3 years ago
- 1 comment
#290 - Rename test package to avoid clash with a malicious pacakge
Pull Request -
State: closed - Opened by bobbyphilip almost 3 years ago
- 2 comments
#289 - Unable to resolve a package by its own name
Issue -
State: open - Opened by fasttime almost 3 years ago
- 2 comments
#288 - Reference to malicious package monorepo-symlink-test causing security scan to fail
Issue -
State: closed - Opened by reify-thomas-smith about 3 years ago
- 4 comments
#287 - missing }
Pull Request -
State: closed - Opened by Bachvonam about 3 years ago
- 1 comment
#286 - Add .npmignore
Pull Request -
State: closed - Opened by JamieMagee about 3 years ago
- 1 comment
#285 - v1.22.1 patch request
Issue -
State: closed - Opened by pos777 about 3 years ago
- 3 comments
#284 - Fix: resolve result is inconsistent with require.resolve if windows virtual drive is used
Pull Request -
State: closed - Opened by pos777 about 3 years ago
#283 - resolve result is inconsistent with require.resolve if windows virtual drive is used
Issue -
State: closed - Opened by pos777 about 3 years ago
- 9 comments
#282 - Added @noflow in malformed package
Pull Request -
State: closed - Opened by sachp1 about 3 years ago
- 2 comments
#281 - do not bundle `tests` directory in npm module
Pull Request -
State: closed - Opened by michaelknoch over 3 years ago
- 1 comment
#280 - Improvement idea - globally configurable helper functions
Issue -
State: open - Opened by naugtur over 3 years ago
- 3 comments
#279 - chore: remove tests from package build
Pull Request -
State: closed - Opened by opravil-jan over 3 years ago
- 2 comments
#278 - Update package.json
Pull Request -
State: closed - Opened by harshit-tv over 3 years ago
- 1 comment
#277 - Exclude non-essential files from published package (especially test/**)
Issue -
State: closed - Opened by broofa over 3 years ago
- 15 comments
#274 - SyntaxError: Unexpected end of JSON input
Issue -
State: closed - Opened by sgurin over 3 years ago
- 5 comments
#273 - [New] add default support for `paths` to include `$HOME/.node_{modules,libraries}`
Pull Request -
State: closed - Opened by ljharb over 3 years ago
- 2 comments
#272 - Fix non-valid values in .editorconfig file
Issue -
State: closed - Opened by funnydino over 3 years ago
- 1 comment
#271 - The test/resolver/malformed_package_json/package.json leads to an fatal error when starting meteor
Issue -
State: closed - Opened by gitJoe42 over 3 years ago
- 39 comments
#270 - Add test malformed_package_json directory to npm ignore to avoid problems with FlowJS
Pull Request -
State: closed - Opened by alexander-schranz over 3 years ago
- 5 comments
#269 - Add test directory to npm ignore to avoid problems with FlowJS
Pull Request -
State: closed - Opened by alexander-schranz over 3 years ago
- 1 comment
#268 - Consider excluding test code from the npm package
Issue -
State: closed - Opened by markstanley-nps over 3 years ago
- 2 comments
#267 - custom path module
Issue -
State: open - Opened by mafintosh over 3 years ago
- 15 comments
#266 - Intentionally malformed package.json causing build errors with meteor
Issue -
State: closed - Opened by DavidShefcik over 3 years ago
- 4 comments
#265 - Error with incorrectly closed json
Issue -
State: closed - Opened by augustofnl over 3 years ago
- 1 comment
#264 - v1.21.0 breaks with next.js, or without graceful-fs upgrade
Issue -
State: closed - Opened by benbender over 3 years ago
- 23 comments
#263 - [actions] fix malformed_package_json package.json bug
Pull Request -
State: closed - Opened by rouftom over 3 years ago
- 2 comments
#262 - intentionally malformed package.json fixture in tests breaks flowtype when checking node_modules
Issue -
State: closed - Opened by paritosh-yadav over 3 years ago
- 9 comments
#261 - not support absolute path?
Issue -
State: closed - Opened by soakit over 3 years ago
- 5 comments
#260 - More detailed not_found error
Pull Request -
State: open - Opened by vansosnin over 3 years ago
#259 - update eslint config
Pull Request -
State: closed - Opened by ljharb over 3 years ago
#258 - Dependency package "path-parse - 1.0.6" is reported as vulnerable by Whitesource scan
Issue -
State: closed - Opened by RajakumarSidhan over 3 years ago
- 1 comment
#256 - Do not throw on missing files in isFile/Dir
Pull Request -
State: closed - Opened by markjm over 3 years ago
- 4 comments
#255 - Use throwIfNoEntry for default isFile and isDirectory
Issue -
State: closed - Opened by markjm over 3 years ago
- 4 comments
#254 - Support browser filed
Issue -
State: closed - Opened by anschm almost 4 years ago
- 1 comment
#253 - `pathFilter` (or some new API) should support implementations of `exports`
Issue -
State: closed - Opened by SimenB almost 4 years ago
- 11 comments
#252 - Version update
Issue -
State: closed - Opened by Avetik666 almost 4 years ago
- 1 comment
#251 - Prioritize moduleDirectory array elements
Issue -
State: closed - Opened by ATheCoder about 4 years ago
- 1 comment
#250 - Multi level "exports" not supported?
Issue -
State: closed - Opened by achingbrain about 4 years ago
- 4 comments
#249 - how to get a version in node .js of a package?
Issue -
State: closed - Opened by cekvenich2 about 4 years ago
- 1 comment
#248 - Update package.json
Pull Request -
State: closed - Opened by scastaldi about 4 years ago
- 9 comments
#247 - path-parse vulnerability
Issue -
State: closed - Opened by isatria about 4 years ago
- 1 comment
#246 - Publish new version of 1.x branch to npm with updated dependency of path-parse
Issue -
State: closed - Opened by shaunek about 4 years ago
- 2 comments
#245 - Update path-parse to 1.0.7 to address CVE-2021-23343
Pull Request -
State: closed - Opened by sethgho about 4 years ago
- 12 comments
#244 - Path parse whitesource issue
Issue -
State: closed - Opened by timjswan about 4 years ago
- 1 comment
#243 - path-parse dependency vulnerability
Issue -
State: closed - Opened by jeffreynerona about 4 years ago
- 2 comments
#242 - + sign in filename breaks vsix extensions
Issue -
State: closed - Opened by echalone about 4 years ago
- 3 comments
#241 - [New] return a promise when resolve is used without callback
Pull Request -
State: closed - Opened by aminya over 4 years ago
#240 - ReDoS in unmaintained path-parse dependency
Issue -
State: closed - Opened by TayHobbs over 4 years ago
- 13 comments
#239 - fix: only include necessary files into npm
Pull Request -
State: closed - Opened by JounQin over 4 years ago
#238 - All files are included into npm
Issue -
State: closed - Opened by JounQin over 4 years ago
- 5 comments
#237 - ReferenceError: process is not defined
Issue -
State: closed - Opened by Profesor08 over 4 years ago
- 1 comment
#236 - [New] add `readPackage` and `readPackageSync`
Pull Request -
State: closed - Opened by SimenB over 4 years ago
- 8 comments
#235 - package is published with all test files
Issue -
State: closed - Opened by jason-ha over 4 years ago
- 14 comments
#234 - Throwing error for an 'invalid main entry'
Pull Request -
State: closed - Opened by Cheesetouched over 4 years ago
- 11 comments
#233 - add 'includeCoreModules' option
Pull Request -
State: closed - Opened by tjenkinson over 4 years ago
- 7 comments
#232 - Add possible error types to README
Pull Request -
State: closed - Opened by joepie91 almost 5 years ago
#231 - bugfix in v1.18 breaks when a core module is not available in a given node version
Issue -
State: closed - Opened by cruzdanilo almost 5 years ago
- 17 comments
#230 - Annoying deprecation warning
Issue -
State: closed - Opened by fvictorio almost 5 years ago
- 3 comments
#229 - Fix "illegal operation on a directory, realpath" on RAM Disk
Pull Request -
State: open - Opened by duykhang53 almost 5 years ago
- 6 comments