![Can not resolve when package.json exports field resolution result is a direcory · Issue #7312 · vitejs/vite · GitHub Can not resolve when package.json exports field resolution result is a direcory · Issue #7312 · vitejs/vite · GitHub](https://user-images.githubusercontent.com/20639676/158142665-9b341ebd-526b-48f2-8f1b-8be316fc2a32.png)
Can not resolve when package.json exports field resolution result is a direcory · Issue #7312 · vitejs/vite · GitHub
GitHub - browserify/browser-resolve: resolve function which support the browser field in package.json
![web3js - Module not found: Error: Can't resolve 'crypto' in '/Users/user/Desktop/esample/react-minting-website/node_modules/eth-lib/lib' - Ethereum Stack Exchange web3js - Module not found: Error: Can't resolve 'crypto' in '/Users/user/Desktop/esample/react-minting-website/node_modules/eth-lib/lib' - Ethereum Stack Exchange](https://i.stack.imgur.com/Rp46M.png)
web3js - Module not found: Error: Can't resolve 'crypto' in '/Users/user/Desktop/esample/react-minting-website/node_modules/eth-lib/lib' - Ethereum Stack Exchange
GitHub - stefanpenner/resolve-package-path: a special purpose fast memoizing way to resolve a node modules package.json
![Jarred Sumner on Twitter: "next version of bun.js gets import.meta.resolve("./path") includes builtin support for: - typescript & tsconfig.json "paths" - package.json "exports" - npm packages & CommonJS-style index.js imports - file extension Jarred Sumner on Twitter: "next version of bun.js gets import.meta.resolve("./path") includes builtin support for: - typescript & tsconfig.json "paths" - package.json "exports" - npm packages & CommonJS-style index.js imports - file extension](https://pbs.twimg.com/media/FOGSg8XVUAIBsg3.jpg:large)
Jarred Sumner on Twitter: "next version of bun.js gets import.meta.resolve("./path") includes builtin support for: - typescript & tsconfig.json "paths" - package.json "exports" - npm packages & CommonJS-style index.js imports - file extension
![package.json was successfully found however this package itself specifies a main module field that could not be resolved · Issue #4516 · lodash/lodash · GitHub package.json was successfully found however this package itself specifies a main module field that could not be resolved · Issue #4516 · lodash/lodash · GitHub](https://user-images.githubusercontent.com/32276134/66707115-668e8800-ed59-11e9-82ae-dbe573e8e86e.png)