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
The Dexie typescript definition file indicates that Dexie is exported as the default export and as 'Dexie' named export but the real javascript module only expose it as the default export.
So this:
import{Dexie}from'Dexie';
causes this error while bundling:
export 'Dexie' was not found in 'dexie'
but typescript is not complaining.
The text was updated successfully, but these errors were encountered:
If we'd export {Dexie} together with export default Dexie in index.ts we create problems for rollup to generate the UMD version. For UMD outputs, rollup handles the case when only a default export is used so it is similar to module.exports = Dexie. Having a mixed export would require the UMD to let the final exported module become {Dexie: Dexie, default: Dexie}, which works bad for UMD exports.
I think it's fixable if we separate the UMD and ES builds a bit (different module entries and different rollup configs).
Working on it.
Hello,
The Dexie typescript definition file indicates that Dexie is exported as the default export and as 'Dexie' named export but the real javascript module only expose it as the default export.
So this:
causes this error while bundling:
but typescript is not complaining.
The text was updated successfully, but these errors were encountered: