Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug Report][3.3.1] Webpack error: Module not found: Error: Default condition should be last one #17436

Closed
lephro opened this issue May 23, 2023 · 1 comment · Fixed by #17439
Labels
framework Issues and Feature Requests that have needs framework-wide. T: bug Functionality that does not work as intended/expected
Milestone

Comments

@lephro
Copy link
Contributor

lephro commented May 23, 2023

Webpack-Vuetify projects are currently (3.3.1) not compiling and throwing an error
Module not found: Error: Default condition should be last one Did you mean './vuetify'?"

This can be easily fixed by reordering the default condition (see link below) to be the last one.

"default": "./lib/framework.mjs",

@lephro lephro changed the title (3.3.1) Webpack error: Module not found: Error: Default condition should be last one [Bug Report][3.3.1] Webpack error: Module not found: Error: Default condition should be last one May 23, 2023
@KaelWD KaelWD added T: bug Functionality that does not work as intended/expected framework Issues and Feature Requests that have needs framework-wide. labels May 24, 2023
@KaelWD KaelWD added this to the v3.3.x milestone May 24, 2023
@bkilinc
Copy link

bkilinc commented May 25, 2023

This breaks our builds. Currently this is the latest release in npmjs. It would be great to have a quick release with this fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
framework Issues and Feature Requests that have needs framework-wide. T: bug Functionality that does not work as intended/expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants