PlasmoHQ
[BUG] 🔴 ERROR | Failed to resolve '../../popup.tsx' from './.plasmo/static/popup.tsx'
What happened?
When I run npm run build, I am receiving this error:
🔴 ERROR | Failed to resolve '../../popup.tsx' from './.plasmo/static/popup.tsx'
The file path is correct, I have my popup.tsx in the root and here's what in popup.tsx.:
import { useReducer } from 'react';
import './style.css';
export default function IndexPopup() {
const [count, increase] = useReducer((c) => c + 1, 0);
return (
<button
onClick={() => increase()}
type="button"
className="inline-flex items-center px-5 py-2.5 text-sm font-medium text-center text-white bg-blue-700 rounded-lg hover:bg-blue-800 focus:ring-4 focus:outline-none focus:ring-blue-300 dark:bg-blue-600 dark:hover:bg-blue-700 dark:focus:ring-blue-800"
>
Hello World
<br />
Count:
<span className="inline-flex items-center justify-center w-8 h-4 ml-2 text-xs font-semibold text-blue-800 bg-blue-200 rounded-full">
{count}
</span>
</button>
);
}
I have no problem with the dev build but this error raises for production. I would greatly appreciate any insights on this matter. Thanks!
Version
Latest
What OS are you seeing the problem on?
MacOSX
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
(OPTIONAL) Contribution
- [ ] I would like to fix this BUG via a PR
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
- [X] I checked the current issues for duplicate problems.
Great question and thanking for putting it forward! I encountered the same issue... Hope someone knows how to resolve this.
I was using node version 22.1.6 and experiencing this issue. After changing the node version to 18.20, the problem no longer occurred!
I was using node version 22.1.6 and experiencing this issue. After changing the node version to 18.20, the problem no longer occurred!
same error in node v18.20
I'm here for the same reason: the dev build works, but the prod build won't compile. I tried versions from 18 to 20, but it didn't work.
We're seeing this as well - node 22.11 here. Is this consistently reproducible using any set of options?
Same issue. Has anyone solved this problem?
I solved it by creating a new project, moving all code, and installing the packages one by one.
I remove "engines": { "node": ">=18" } in package.json, solved this error
YES！Thank you!
Probably your "main" is populated, remove that from package.json it will be fixed.
Getting this too! here's an example repo, fixed by remoing the engines from package.json as @fangmd suggested (Thanks!)
