-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Remix server timeout #7332
Comments
I tried downgrading Remix, same result. |
I believe it is indeed the // remix.config.js
/** @type {import('@remix-run/dev').AppConfig} */
module.exports = {
future: {
unstable_postcss: true
},
server: './server.js',
serverMinify: true,
ignoredRouteFiles: ['**/__snapshots__/**', '**/.*', '**/*.test.tsx', '**/*.test.ts'],
appDirectory: 'src',
serverBuildDirectory: "server",
browserBuildDirectory: "public/build",
serverBuildPath: "server/index.js",
publicPath: "/_static/build",
}; // server.js
import { createRequestHandler } from '@remix-run/architect';
import * as build from '@remix-run/dev/server-build';
export const handler = createRequestHandler({
build: build,
mode: process.env.NODE_ENV
}); |
Related: #6062 |
I think #6062 covers it - so going to close this issue. We are blocked by for server-side support for lambda, but client side should be fine. You could try instrumenting it yourself using our Serverless SDK. https://docs.sentry.io/platforms/node/guides/aws-lambda/ |
I tried this and unfortunately it has yielded the same result. Client support is ok for now, I'll keep an eye on #6062. Thanks ^^ |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using? If you use the CDN bundles, please specify the exact bundle (e.g.
bundle.tracing.min.js
) in your SDK setup.@sentry/remix
SDK Version
7.40.0
Framework Version
Remix 1.13.0
Link to Sentry event
No response
SDK Setup
It might be worth mentioning that I use
"@architect/architect": "^10.10.2",
to server the dev server as it provides a nice emulation of the AWS Lambda environment which is the destination for this.Steps to Reproduce
npm run dev
Expected Result
Expecting the index page to load
Actual Result
When opening the page, it times out
This is the log in the server console.
If I comment out the Sentry.init in the
entry.server.tsx
, the client works and generating an error on the client goes through to Sentry. No joy on the server thoughThe text was updated successfully, but these errors were encountered: