Exporting commonjs module with Object.assign instead of Object.create to improve property visibility during development

This commit is contained in:
Ben Ashton 2021-03-14 21:22:36 -07:00
parent 7501617e1e
commit 22f2060a1e
3 changed files with 7 additions and 11 deletions

View File

@ -585,11 +585,9 @@ __webpack_require__.r(__webpack_exports__);
/* harmony default export */ const __WEBPACK_DEFAULT_EXPORT__ = (Object.create(_pawsqlite_mjs__WEBPACK_IMPORTED_MODULE_0__.PawSQLite, { /* harmony default export */ const __WEBPACK_DEFAULT_EXPORT__ = (Object.assign({
Error: { Error: _pawsqlite_error_mjs__WEBPACK_IMPORTED_MODULE_1__.PawSQLiteError
value: _pawsqlite_error_mjs__WEBPACK_IMPORTED_MODULE_1__.PawSQLiteError }, _pawsqlite_mjs__WEBPACK_IMPORTED_MODULE_0__.PawSQLite));
}
}));
})(); })();
module.exports = __webpack_exports__.default; module.exports = __webpack_exports__.default;

File diff suppressed because one or more lines are too long

View File

@ -1,8 +1,6 @@
import { PawSQLite } from "./pawsqlite.mjs"; import { PawSQLite } from "./pawsqlite.mjs";
import { PawSQLiteError } from "./pawsqlite_error.mjs"; import { PawSQLiteError } from "./pawsqlite_error.mjs";
export default Object.create(PawSQLite, { export default Object.assign({
Error: { Error: PawSQLiteError
value: PawSQLiteError }, PawSQLite);
}
});