Open ncoquelet opened 4 months ago
vikinatora
commented
4 months ago You should probably use the browser preset from here: https://github.com/typicode/lowdb/blob/main/src/examples/browser.ts
Also, https://github.com/ncoquelet/lowdb_esm_issue is private
ncoquelet
commented
4 months ago I have try the browser preset but globaly I obtains the same issues. This is a problem with node and esm, my repo is now public to quickly reproduce my state. Thanks for your support
MisterrrX
commented
2 months ago Got the same issue using Typescript, Webpack and node with ESM. Have you found any fix for this @ncoquelet?
ncoquelet
commented
2 months ago Got the same issue using Typescript, Webpack and node with ESM. Have you found any fix for this @ncoquelet?
Nop, I'm using something else ...
shaman-apprentice
commented
1 week ago My workaround for NestJS - maybe it is useful for someone else as well:
// use dynamic imports in combination with TS `moduleResolution: Node16` in ts config
const { JSONFilePreset } = await import("lowdb/node");
Hi,
I've been stuck for two days trying anything to add lowdb to my project, and this issue is my last chance. This is a full ESM project using full Typescript and based on react, nextjs and jest.
I've created a repo that reproduce the problem by simplified the dependencies and customisation to avoid side effects. https://github.com/ncoquelet/lowdb_esm_issue
Installation
Problems
Without lowdb everything works fine, but when I instantiate any lowdb class, I get these errors, both in next build and in the jest execution.
During Next build
full log
```shell lowdb_esm_issue@0.1.0 build next build ▲ Next.js 14.2.3 Creating an optimized production build ... Failed to compile. node:fs/promises Module build failed: UnhandledSchemeError: Reading from "node:fs/promises" is not handled by plugins (Unhandled scheme). Webpack supports "data:" and "file:" URIs by default. You may need an additional plugin to handle "node:" URIs. at /home/john/dev/projects/lowdb_esm_issue/node_modules/next/dist/compiled/webpack/bundle5.js:28:401757 at Hook.eval [as callAsync] (eval at create (/home/john/dev/projects/lowdb_esm_issue/node_modules/next/dist/compiled/webpack/bundle5.js:13:28858),Jest Execution
full log
```shell lowdb_esm_issue@0.1.0 test jest FAIL src/app/Repository.test.ts ● Test suite failed to run Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /home/john/dev/projects/lowdb_esm_issue/node_modules/lowdb/lib/node.js:1 ({"Object.