Issue react-md-editor@4.0.5 - Expected usable value but received an empty preset

[volosincu]

I had this error. Could not find the cause but I think it is caused by the module type.
In the project I'm using react-markdown with rehype plugins and there unified doesn't have this issues.

index.js:1110 Uncaught (in promise) Error: Expected usable value but received an empty preset, which is probably a mistake: presets typically come with `plugins` and sometimes with `settings`, but this has neither
    at addPreset (index.js:1110:1)
    at apply.use (index.js:1076:1)
    at ./node_modules/@uiw/react-md-editor/esm/index.js (index.js:10:1)
    at __webpack_require__ (bootstrap:19:1)
    at sharing:50:1
    at __webpack_require__.m.<computed> (main.js:494:34)
    at __webpack_require__ (bootstrap:19:1)

ts-config

{
  "compilerOptions": {
    "jsx": "react",
    "module": "ESNext",
    "noImplicitAny": true,
    "outDir": "./build/",
    "preserveConstEnums": true,
    "removeComments": true,
    "sourceMap": true,
    "target": "es5",
    "esModuleInterop": true,
    "moduleResolution": "bundler",
    "resolveJsonModule": true,
    "allowSyntheticDefaultImports": true,
    "typeRoots": ["node_modules/@types", "./src/@types"]
  },
  "include": ["src/**/*", ".eslintrc.js"],
  "exclude": ["node_modules"]
}

[jaywcjlove]

react-md-editor/tsconfig.json

Lines 1 to 22 in a48e36f

	{
	"compilerOptions": {
	"target": "es5",
	"lib": ["dom", "dom.iterable", "esnext"],
	"allowJs": true,
	"skipLibCheck": true,
	"esModuleInterop": true,
	"allowSyntheticDefaultImports": true,
	"strict": true,
	"forceConsistentCasingInFileNames": true,
	"module": "esnext",
	"moduleResolution": "node",
	"resolveJsonModule": true,
	"isolatedModules": true,
	"declaration": true,
	"baseUrl": ".",
	"jsx": "react-jsx",
	"noFallthroughCasesInSwitch": true,
	"noEmit": true,
	"types": ["jest", "node"]
	}
	}

I also use the ESNext module, but I haven’t encountered this issue in my project. I’m not sure how to resolve your problem. I recommend checking the versions of react-md-editor and the related plugins, or trying to adjust the module configuration to see if it helps. @volosincu