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

[Bug?]: node adaptor wrong content type header #1112

Closed
2 tasks done
shawnyu5 opened this issue Nov 4, 2023 · 2 comments
Closed
2 tasks done

[Bug?]: node adaptor wrong content type header #1112

shawnyu5 opened this issue Nov 4, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@shawnyu5
Copy link

shawnyu5 commented Nov 4, 2023

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Current behavior 😯

Trying to deploy a solid js app, with the node adapter in kubernetes. Getting the following error when I open the application in the browser:

Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.

Most things I've read tells me this is most likely an application issue, that the server should be configured properly to set the correct content type headers. However this behavior only happens when the app is deployed in K8s, not locally, or deployed in vercel.

Expected behavior 🤔

The app should load as normal

Steps to reproduce 🕹

Steps:

  1. Create a k8s deployment, and a Service pointing to the deployment.
  2. Set up an ingress to be able to access the app on the local web browser.
  3. Open app in local web browser

Context 🔦

Trying to deploy the application in Kubernetes

Your environment 🌎

System:
 OS: arch
Binaries:
 Node: v20.9.0
@shawnyu5 shawnyu5 added the bug Something isn't working label Nov 4, 2023
@shawnyu5
Copy link
Author

shawnyu5 commented Nov 4, 2023

Just tried the same deployment method with a next js app. it is able to deploy successfully. This leads me to believe its the node adaptor not setting the right content headers

@ryansolid
Copy link
Member

In setting up for SolidStart's next Beta Phase built on Nitro and Vinxi we are closing all PRs/Issues that will not be merged due to the system changing. If you feel your issue was closed by mistake. Feel free to re-open it after updating/testing against 0.4.x release. Thank you for your patience.

See #1139 for more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants