browserify/resolve

Issues

• Provide canonical resolution resource for malicious code flag

  #326 opened 4 months ago by duncanhall
  5

• Package includes test folder

  #322 opened a year ago by johnlister
  4

• Critical Vulnerability with monorepo-symlink-test

  #318 opened a year ago by bbuck
  8

• Any reason to publish /test?

  #323 opened a year ago by vvscode
  5

• The test/resolver/malformed_package_json/package.json leads to an fatal error when starting meteor

  #271 opened a year ago by gitJoe42
  39

• `npx resolve` errors

  #315 opened a year ago by vvscode
  17

• monorepo-symlink-test security issue

  #319 opened a year ago by avosper-intellaegis
  1

• Critical Vulnerability reported on monorepo-symlink-test - False Negative

  #317 opened a year ago by bzemms
  1

• Incorrect work on Linux (`Error: `resolve` must be run directly as an executable`)

  #316 opened a year ago by vvscode
  0

• [Security] Malicious code in `test/resolver/multirepo`

  #309 opened a year ago by aashutoshrathi
  19

• monorepo-symlink-test

  #312 opened a year ago by roberthockley
  5

• Used monorepo-symlink-test is malicious

  #314 opened a year ago by ThomazPom
  1

• Critical vulnerability monorepo-symlink-test

  #311 opened a year ago by Iuriy-Budnikov
  2

• Critical Vulnerability due to Resolve Package -- monorepo-symlink-test

  #310 opened a year ago by kjcohen
  2

• Error "ENOENT: no such file or directory, open '../../is-core-module/core.json"

  #297 opened a year ago by SuperOleg39
  20

• This package is being flagged as malware - false positive

  #306 opened 2 years ago by chiahrens
  1

• The 'test' directory seems to contain the code of malicious package 'monorepo-symlink-test'

  #305 opened 2 years ago by lanzkron
  1

• Resolve monorepo-symlink-test vulnerable package

  #304 opened 2 years ago by frabbiDAndT
  1

• monorepo-symlink-test GHSA-2jcg-qqmg-46q6 Vulnerability

  #303 opened 2 years ago by castafab
  9

• Remove readFileSync

  #302 opened 2 years ago by polRk
  1

• WebpackError: TypeError: Unable to determine current node version

  #301 opened 2 years ago by sherlockfeng
  0

• Question: NPM version 1.22.3 is published but 1.22.2 is marked as `latest`

  #298 opened 2 years ago by akphi
  1

• Result differs from Node's require.resolve when using `basedir` option with symlinks

  #295 opened 2 years ago by j-christoffersen
  9

• Unexpected end of input, expected the token `}`

  #294 opened 2 years ago by AndyFang36
  3

• Please make async resolve mockable with pure sinon

  #293 opened 2 years ago by art-alexeyenko
  1

• Unable to resolve a package by its own name

  #289 opened 2 years ago by fasttime
  2

• Question around dummy packages in monorepo test

  #292 opened 2 years ago by plygrnd
  3

• Remove npm package monorepo-symlink-test (contains malicious code)

  #291 opened 2 years ago by muhanator
  1

• Reference to malicious package monorepo-symlink-test causing security scan to fail

  #288 opened 2 years ago by reify-thomas-smith
  4

• resolve result is inconsistent with require.resolve if windows virtual drive is used

  #283 opened 3 years ago by pos777
  9

• v1.22.1 patch request

  #285 opened 3 years ago by pos777
  3

• Exclude non-essential files from published package (especially test/**)

  #277 opened 3 years ago by broofa
  15

• Consider excluding test code from the npm package

  #268 opened 3 years ago by markstanley-nps
  2

• Improvement idea - globally configurable helper functions

  #280 opened 3 years ago by naugtur
  3

• `pathFilter` (or some new API) should support implementations of `exports`

  #253 opened 3 years ago by SimenB
  11

• custom path module

  #267 opened 3 years ago by mafintosh
  15

• SyntaxError: Unexpected end of JSON input

  #274 opened 3 years ago by sgurin
  5

• intentionally malformed package.json fixture in tests breaks flowtype when checking node_modules

  #262 opened 3 years ago by paritosh-yadav
  9

• Fix non-valid values in .editorconfig file

  #272 opened 3 years ago by funnydino
  1

• v1.21.0 breaks with next.js, or without graceful-fs upgrade

  #264 opened 3 years ago by benbender
  23

• Intentionally malformed package.json causing build errors with meteor

  #266 opened 3 years ago by DavidShefcik
  4

• Error with incorrectly closed json

  #265 opened 3 years ago by augustofnl
  1

• Prioritize moduleDirectory array elements

  #251 opened 3 years ago by ATheCoder
  1

• not support absolute path?

  #261 opened 3 years ago by soakit
  5

• Dependency package "path-parse - 1.0.6" is reported as vulnerable by Whitesource scan

  #258 opened 3 years ago by RajakumarSidhan
  1

• Use throwIfNoEntry for default isFile and isDirectory

  #255 opened 3 years ago by markjm
  4

• Support browser filed

  #254 opened 3 years ago by anschm
  1

• Version update

  #252 opened 3 years ago by Avetik666
  1

• Multi level "exports" not supported?

  #250 opened 3 years ago by achingbrain
  4

• how to get a version in node .js of a package?

  #249 opened 4 years ago by cekvenich2
  1