You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrading from 3.0.3 to 3.0.2 my webpack 5 / Yarn 2 build starts to fail with:
ERROR in ./ClientApp/.../dexieDB.js 3:0-26
Module not found: Error: Package path ./dist/dexie.js is not exported from package
...Repo\.yarn\cache\dexie-npm-3.2.0-575507c806-59b6fd600a.zip\node_modules\dexie\
(see exports field in ... node_modules\dexie\package.json)
If I look up the differences between those two package.json files, the error is caused by the addition in 3.2.0 of an "exports", viz: "exports": "./dist/modern/dexie.mjs",
The new "exports" entry explicitly exports "dexie.mjs", where as my webpack/ yarn2 stuff is apparently expecting dexie.js, as the error message suggests. My import has been: import Dexie from 'dexie';
Upgrading from 3.0.3 to 3.0.2 my webpack 5 / Yarn 2 build starts to fail with:
If I look up the differences between those two package.json files, the error is caused by the addition in 3.2.0 of an "exports", viz:
"exports": "./dist/modern/dexie.mjs",
The new "exports" entry explicitly exports "dexie.mjs", where as my webpack/ yarn2 stuff is apparently expecting dexie.js, as the error message suggests. My import has been:
import Dexie from 'dexie';
The release notes: https://github.com/dfahlander/Dexie.js/releases don't mention this specifically.
This is the change wot broke me build.
I can probably alias it somehow, but maybe I'm doing something stupid?
Update: yes, it's my stupidity:
I was aliasing to dexie.js, not dexie.mjs, so that'd cause this. Please close!
The text was updated successfully, but these errors were encountered: