[ERROR] Could not resolve "react" / "react-dom"
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react
- Domain
- build-system, frontend
Research direction
Reproduce the reported remix dev build and inspect ../node_modules/@grapesjs/react/dist/index.js, where imports of react and react-dom fail to resolve. Determine the package or setup change needed so both imports resolve, then confirm the Remix build completes without these errors.
Written by the indexing model from the issue text.
Description
Doesn't seem to work with Remix, get the following errors. I've tried a number of workarounds with no prevail. Any suggestions on how to remedy these errors?
11:21:51 │ remix │
11:21:51 │ remix │ 💿 remix dev
11:21:51 │ remix │
11:21:51 │ webhooks │ Sending APP_UNINSTALLED webhook to app server
11:21:51 │ remix │ info building...
11:21:52 │ remix │ ✘ [ERROR] Could not resolve "react"
11:21:52 │ remix │
11:21:52 │ remix │ ../node_modules/@grapesjs/react/dist/index.js:1:150:
11:21:52 │ remix │ 1 │ ...as C, memo as A, useMemo as Ne, createElement as Ve } from "react";
11:21:52 │ remix │ ╵ ~~~~~~~
11:21:52 │ remix │
11:21:52 │ remix │ You can mark the path "react" as external to exclude it from the bundle, which will remove this error.
11:21:52 │ remix │
11:21:52 │ remix │
11:21:52 │ remix │ ✘ [ERROR] Could not resolve "react-dom"
11:21:52 │ remix │
11:21:52 │ remix │ ../node_modules/@grapesjs/react/dist/index.js:2:35:
11:21:52 │ remix │ 2 │ import { createPortal as Tt } from "react-dom";
11:21:52 │ remix │ ╵ ~~~~~~~~~~~
11:21:52 │ remix │
11:21:52 │ remix │ You can mark the path "react-dom" as external to exclude it from the bundle, which will remove this error.
11:21:52 │ remix │
11:21:52 │ remix │
- Dominant language
- TypeScript
- Stars
- 183
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GrapesJS/react
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·