Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: (0 , import_jsx_dev_runtime.jsxDEV) is not a function #5743

Closed
1 task done
binajmen opened this issue Mar 9, 2023 · 3 comments
Closed
1 task done

TypeError: (0 , import_jsx_dev_runtime.jsxDEV) is not a function #5743

binajmen opened this issue Mar 9, 2023 · 3 comments
Assignees

Comments

@binajmen
Copy link
Contributor

binajmen commented Mar 9, 2023

What version of Remix are you using?

1.14.0

Are all your remix dependencies & dev-dependencies using the same version?

  • Yes

Steps to Reproduce

    "dev": "run-p dev:*",
+    "dev:build": "cross-env NODE_ENV=development remix dev",
+    "dev:serve": "cross-env NODE_ENV=development nodemon --watch build server.js",
-    "dev:server": "cross-env NODE_ENV=development node --inspect --require ./node_modules/dotenv/config --require ./mocks ./build/server.js",
-    "dev:build": "cross-env NODE_ENV=development npm run build:server -- --watch",
-    "dev:remix": "cross-env NODE_ENV=development remix watch",
    "dev:css": "cross-env NODE_ENV=development npm run generate:css -- --watch",

Expected Behavior

HMR is working without errors

Actual Behavior

Getting this error:

TypeError: (0 , import_jsx_dev_runtime.jsxDEV) is not a function
    at /Users//Projects//app/entry.server.tsx:64:9
    at new Promise (<anonymous>)
    at handleRequest (/Users//Projects//app/entry.server.tsx:59:10)
    at handleDocumentRequestRR (/Users//Projects//build/server.js:38925:18)
    at requestHandler (/Users//Projects//build/server.js:38787:22)
    at /Users//Projects//build/server.js:39945:26
@kiliman
Copy link
Collaborator

kiliman commented Mar 9, 2023

Yes, I'm getting that also with Remix App Server. Switching to Express works.

@MichaelDeBoey
Copy link
Member

MichaelDeBoey commented Mar 9, 2023

This will be fixed by @mcansh's #4358

@pcattori
Copy link
Contributor

pcattori commented May 3, 2023

This was caused by NODE_ENV being set differently across different builds. The new dev server ensures NODE_ENV=development is set for all builds while it is running. Fixed in v1.16.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants