wooorm/import-meta-resolve

Issues

• Async API for moduleResolve()?

  #29 opened 5 months ago by justinfagnani
  3

• Make this work with yarn berry (aka yarn 2/3/4)

  #26 opened 9 months ago by francisu
  7

• [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated in Node v22.0.0

  #27 opened 8 months ago by IronGeek
  4

• unexpected `ERR_PACKAGE_PATH_NOT_EXPORTED` thrown

  #24 opened 10 months ago by JounQin
  8

• Incompatible with yarn P'n'P

  #23 opened 10 months ago by JounQin
  12

• Yarn PnP compatibility?

  #10 opened 2 years ago by bencmbrook
  18

• Resolve fails on MacOS and Windows, works on linux

  #22 opened a year ago by dcarniel-ipepper
  7

• First item is always resolved when export map target is Array (even if non-existent)

  #20 opened a year ago by helmturner
  8

• Support for resolving modules from folder paths

  #19 opened a year ago by fabiospampinato
  8

• exporting the `packageResolve` function

  #18 opened a year ago by sheerlox
  2

• Possible to use worker threads and execArgv?

  #17 opened a year ago by jcbhmr
  14

• `import.meta.resolve` is now defined to be _sync_

  #14 opened 2 years ago by giltayar
  1

• Circular dependency in lib/get-format.js

  #12 opened 2 years ago by brawaru
  1

• Support for TypeScript files

  #5 opened 3 years ago by ifiokjr
  13

• Want help on maintenance?

  #11 opened 2 years ago by pi0
  4

• Use module.builtinModules instead of builtins dependency

  #7 opened 2 years ago by calebeby
  1

• how to resolve named exports?

  #8 opened 2 years ago by lili21
  5

• Enabling usage of this package in an eslint plugin

  #2 opened 3 years ago by giltayar
  8

• Issues with loading from ESM, "type": "module", & rollup

  #1 opened 3 years ago by btakita
  2