ERROR: Could not resolve webpack

blouflashdb commented 1 year ago

Reporting a bug?

I am using import VueI18nVitePlugin from "@intlify/unplugin-vue-i18n/vite"; vite: { resolve: { alias: { "vue-i18n": "vue-i18n/dist/vue-i18n.runtime.esm-bundler.js", }, }, plugins: [ svgLoader(), VueI18nVitePlugin({ include: [ resolve(dirname(fileURLToPath(import.meta.url)), "./locales/*.json"), ], }), ], },

and when I open my App I get an error that webpack is not installed but I am using vite.

Expected behavior

No Error

Reproduction

See code above.

Issue Package

unplugin-vue-i18n

System Info

System:
    OS: Windows 10 10.0.22621
    CPU: (12) x64 AMD Ryzen 5 5500
    Memory: 8.87 GB / 15.90 GB
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.819.0), Chromium (107.0.1418.42)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    vue-i18n: ^9.2.2 => 9.2.2

Screenshot

No response

Additional context

[vite] error while updating dependencies: 19:31:48
Error: Build failed with 3 errors: node_modules/@intlify/unplugin-vue-i18n/lib/index.mjs:454:27: ERROR: Could not resolve "webpack" node_modules/esbuild/lib/main.js:1327:21: ERROR: [plugin: vite:dep-pre-bundle] Failed to resolve entry for package "@intlify/shared". The package may have incorrect main/module/exports specified in its package.json: No known conditions for "." entry in "@intlify/shared" package node_modules/esbuild/lib/main.js:1327:21: ERROR: [plugin: vite:dep-pre-bundle] Failed to resolve entry for package "@intlify/shared". The package may have incorrect main/module/exports specified in its package.json: No known conditions for "." entry in "@intlify/shared" package

Validations

[X] Read the Contributing Guidelines.
[X] Read the README
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.

kazupon commented 1 year ago

Thank you for your reporting!

Could you give us minimum reproduction code via GitHub or StackBliz plaese? 🙏

Issue reporting guidline said:

Please provide a link to a repo that can reproduce the problem you ran into. A reproduction is required unless you are absolutely sure that the issue is obvious and the provided information is enough to understand the problem. If a report is vague (e.g. just a generic error message) and has no reproduction, it will receive a "Status: Need More Info" label. If no reproduction is provided after 5 days, it will be closed.

Ref blog article: https://antfu.me/posts/why-reproductions-are-required

dargmuesli commented 1 year ago

I reproduced the same problem in a larger code base, but were not able to create a minimum reproduction until now.

phamhongphuc commented 1 year ago

Hi, I also got the same issue when trying to setup my new project with Nuxt 3. I realized the problem appeared when I tried to combine the following tools:

Node: 16x or 18x.
Package management:
- Yarn: both old yarn (1.x) and new yarn (3.x without pnp) get the same error
- Npm: using npm in Stackblitz gives a different error
Nuxt 3 with Vite
Vue i18n: unplugin-vue-i18n.
TailwindCSS: both official instructions or using @nuxtjs/tailwindcss give me the same error
- Official installation docs: https://tailwindcss.com/docs/guides/nuxtjs#3
- Nuxt Tailwind: https://github.com/nuxt-modules/tailwindcss

Both unplugin-vue-i18n and @nuxtjs/tailwindcss work fine alone but when installing both in the repo the issue appears. The issue only appears when calling nuxt dev but not when calling nuxt build.

This is a minimum reproduction on StackBlitz: https://stackblitz.com/edit/nuxt3-issue-unplugin-vue-i18n

Image

![stackblitz com_edit_nuxt3-issue-unplugin-vue-i18n_file=package json](https://github.com/intlify/bundle-tools/assets/11532116/c5c9c1bb-abee-448c-a3cd-985e7e65f247)

Dorianslavov commented 1 year ago

Experiencing this issue too. Trying to migrate nuxt 2 project to nuxt 3. I've also removed @nuxtjs/tailwindcss as above comment suggested but nothing changed. @kazupon please review this issue as it's a huge blocker which basically makes this unusable

DeivTorres commented 1 year ago

I have the same issue. Seems to be no news on this :(

intlify / bundle-tools