[vite] - No matching export for import pathToFileUrl

[jdmorlan]

I'm using ViteJS as the build tool for a React application. When I try to run the vite dev server I get the error referenced in the title above. I'm not very well versed in the workings of awilix, but attempted to Google for that error. I was able to find a couple of things about loadModules and Windows tests, but didn't seem to match this issue.

I setup a repo that isolates vite, awilix and jishida/react-awilix. I'm more than willing to do more investigating, but I'm kind of stuck with what to attempt next. Any help or advice would be greatly appreciated.

Error Message

[jeffijoe]

You need to configure your build tool to use the browser build.

[simonvizzini]

Hi @jdmorlan, I know it's been a while when you asked this question but I'm facing the same issue. Have you ever figured out how to properly configure Vite to make it work with Awilix? I know that Vite is using esbuild under the hood and esbuild has a platform option which can be set to node or browser, but it doesn't seem to be directly exposed in the Vite config. Closes thing I have found is the optimizeDeps.esbuildOptions Vite option which does exposes the platform option from esbuild, but setting it to browser didn't change anything, Vite is still using the node-only lib/awilix.module bundle instead of the lib/awilix.browser bundle.

Only workaround I found so far is to directly import the browser bundle in my code. Typescript then complains but at least it is still getting built.

[downace]

I've faced similar issue.

Added alias in my vite.config.ts to make it work:

export default {
  resolve: {
    alias: {
      'awilix': 'awilix/lib/awilix.browser'
    }
  }
}

Maybe it should be noted in the docs...

[jeffijoe]

I would think it's something that should be fixed on Vite's side? Webpack resolves the browser build by default just fine.

[downace]

I would think it's something that should be fixed on Vite's side? Webpack resolves the browser build by default just fine.

Ah, I think I got it. Found this open issue in Vite repo: vitejs/vite#7576. Looks like the problem is the same.