All Issues
24,993 verified issues
[NEXT-1314] High memory usage in deployed Next.js project
Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information [code block] Which area(s) of Next.js are affected? (leave empty if unsure) _No response_ Link to the code that reproduces this issue https://codesandbox.io/p/github/ProchaLu/next-js-ram-example/ To Reproduce - Clone the repository: https://github.com/ProchaLu/next-js-ram-example - Deploy the project on Fly.io Describe the Bug I have been working on a small project to reproduce an issue related to memory usage in Next.js. The project is built using the Next.js canary version `13.4.3-canary.1`. It utilizes Next.js with App Router and Server Actions and does not use a database. The problem arises when deploying the project on different platforms and observing the memory usage behavior. I have deployed the project on multiple platforms for testing purposes, including Vercel and Fly.io. - On Vercel: https://next-js-ram-example.vercel.app/ When interacting with the deployed version on Vercel, the project responds as expected. The memory usage remains stable and does not show any significant increase or latency - On Fly.io: https://memory-test.fly.dev/ However, when deploying the project on Fly.io, I noticed that the memory usage constantly remains around 220 MB, even during normal usage scenarios Expected Behavior I expect the small project to run smoothly without encountering any memory-related issues when deployed
HTTP Keep-alive, "socket hang up" ECONNERR on a long-running second request
Describe the bug On keep-alive connections, if a timeout value is given to the first request but not on subsequent requests, the subsequent requests will eventually throw a "socket hang up" error. To Reproduce [code block] Code snippet _No response_ Expected behavior 1. "socket hang up" is misleading because it indicates the server closed the connection (in this bug the opposite is true) 2. One would not expect that a timeout would keep running after a request has completed. This is a (quite major IMO) footgun. Axios Version 0.22.0 - 1.6.2 Adapter Version HTTP Browser _No response_ Browser Version _No response_ Node.js Version 20.9.0 OS OSX 14 Additional Library Versions _No response_ Additional context/Screenshots <img width="1456" alt="tcpdump" src="https://github.com/axios/axios/assets/100387231/a64c6544-4551-46ad-bb3e-1d9a6e9102b6">
Mongoose 4.6.2 produces error "MongoError: no primary found in replicaset" while 4.4.19 works just fine
Simple connection to a MongoDB replica set. Works great in Mongoose 4.4.19 but not in 4.6.2 mongoURI = "mongodb://IP:27017,IP:27017/" + dbName + "?replicaSet=my_replica_set"; Using 4.6.2, I have tried the following: - defining replset in connection options - connectWithNoPrimary: true - tried both mongoose.createConnection vs mongoose.connect - included and excluded arbiter node in the connection string If connection string only uses one database, it works fine. I am really curious as to why this error occurs. Any thoughts? Full Error: /Users/adeel/dev/navi/euler/node_modules/mongodb/lib/replset.js:360 process.nextTick(function() { throw err; }) ^ MongoError: no primary found in replicaset at /Users/adeel/dev/navi/euler/node_modules/mongodb-core/lib/topologies/replset.js:631:32 at .<anonymous> (/Users/adeel/dev/navi/euler/node_modules/mongodb-core/lib/topologies/replset.js:421:24) at g (events.js:286:16) at emitOne (events.js:96:13) at emit (events.js:188:7) at .<anonymous> (/Users/adeel/dev/navi/euler/node_modules/mongodb-core/lib/topologies/server.js:313:21) at emitOne (events.js:96:13) at emit (events.js:188:7) at .<anonymous> (/Users/adeel/dev/navi/euler/node_modules/mongodb-core/lib/connection/pool.js:260:12) at g (events.js:286:16) at emitTwo (events.js:106:13) at emit (events.js:191:7) at Socket.<anonymous> (/Users/adeel/dev/navi/euler/node_modules/mongodb-core/li
AWS S3 Sync Issues
There have been a few issues with respect to the `sync` command, particularly in the case of syncing down from S3 (`s3 -> local`). I'd like to try to summarize the known issues as well as a few proposals of possible options, and give people the opportunity to share any feedback they might have. Sync Behavior Overview The sync behavior is intended to be an efficient `cp`; only copy over the files from the source to the destination that are different. In order to do that we need to be able to determine whether or not a file in s3/local are different. To do this, we use two values: - File Size (from `stat`'ing the file locally and from the `Size` key in a `ListObjects` response) - Last modified time (mtime of the local file and the `LastModified` key in a `ListObjects` response) As an aside, we use the `ListObjects` operation because we get up to 1000 objects returned in a single call. This means that we're limited to information that comes back from a `ListObjects` response which is `LastModified, ETag, StorageClass, Key, Owner, Size`. Now given the remote and local files file size and last modified times we try to determine if the file is different. The file size is easy, if the file sizes are different, then we know the files are different and we need to sync the file. However, last modified time is more interesting. While the mtime of the local file is a true mtime, the `LastModified` time from `ListObjects` is really the time the object was uploaded. So imagine t
[BUG] "ERR! Cannot find module 'agentkeepalive'" trying to "npm install -g npm@7.6.0"
As far as I know, this is not: - https://github.com/npm/cli/issues/555 (I don't recall trying to upgrade and breaking anything, previously; plus, npm is not installed as root: if I try the same command with sudo, I get `sudo: npm: command not found`) - https://github.com/npm/cli/issues/2454 (I'm running npm 7.5.3, not 6.x) - https://github.com/npm/cli/issues/1935 (not npx, not CI, just a local Linux environment) Current Behavior: When I open a terminal, I get this message: > npm notice > npm notice New minor version of npm available! 7.5.3 -> 7.6.0 > npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.6.0 > npm notice Run npm install -g npm@7.6.0 to update! > npm notice When I run `npm install -g npm@7.6.0` as it suggests, I get: > npm ERR! code MODULE_NOT_FOUND > npm ERR! Cannot find module 'agentkeepalive' > npm ERR! Require stack: > npm ERR! - /home/me/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/make-fetch-happen/agent.js > npm ERR! - /home/me/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/make-fetch-happen/index.js > npm ERR! - /home/me/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/npm-registry-fetch/index.js > npm ERR! - /home/me/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/pacote/lib/remote.js > npm ERR! - /home/me/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/pacote/lib/git.js > npm ERR! - /home/me/.nvm/versions/node/v12.16.1/lib/node_modules/npm/node_modules/pacote/
[BUG]: RLS Policies not applied with `push` but applied with `migrate`
Report hasn't been filed before. - [x] I have verified that the bug I'm about to report hasn't been filed before. What version of `drizzle-orm` are you using? 0.36.0 What version of `drizzle-kit` are you using? 0.27.2 Other packages _No response_ What is the undesired behavior? Using `drizzle-kit push` does not apply the RLS policy SQL statements correctly. However, using `drizzle-kit generate` and `drizzle-kit migrate` does apply these policies as expected. | Command | Supabase Evidence | |--------|--------| | After running `drizzle-kit push` | | | After running `drizzle-kit generate` and `drizzle-kit migrate` | | What are the steps to reproduce it? - I'm using Supabase with Postgres v15.1.1.47 - I don't think this bug pertains to a driver, see below. - I don't think this bug is related to the runtime, see below. - I'm working on a monorepo, but I isolated this issue in a fresh Supabase project and database, and on a separate repo. Minimal reproducible example package.json [code block] index.ts [code block] drizzle.config.ts [code block] What I've tried to fix it 1. Use the `link` API. index.ts [code block] 2. Use different runtimes: - Node v23.1.0, npm v10.9.0 - Deno v2.0.5 - Bun v1.1.34 - pnpm v9.12.3 3. Use a different driver: package.json [code block] 4. Remove the `entities` property in drizzle.config.ts: drizzle.config.ts [code block] 5. Upgrade Postgres version: - Postgres v15.6.1.135 What is the desired result? I expected `drizzle-kit p
FR: Firestore offline persistence in web workers
Operating System version: n/a Browser version: n/a Firebase SDK version: n/a Firebase Product: firestore Are there any plans to make offline persistence available in web workers? Inspired by @davideast 's article I dropped 95% of my Firebase bundle size using this one weird trick to use firebase in a worker, I've noticed offline persistence isn't available in that context. Browsing the source, I suspect it's the reliance on (and absence in workers of) localStorage that's the issue - so I was wondering if there's any alternative to using synchronous storage in this case? Thanks.
Apache 2.4 ProxyPass Configuration
With 0.9 I was able to proxy our websockets through Apache 2.4 using the following config: [code block] I'm attempting to migrate to 1.0.6 now and I immediately noticed that the socket endpoint changed, but updating the ProxyPass config like so does not seem to do the trick. [code block] Chrome reports over and over again that it receives a 400 error when trying to open the websocket. There's no output in the console on the server to indicate that any connection attempt was received (DEBUG=socket.io). Is there some other configuration factor that I need for this to work?
Error: timeout of 0ms exceeded
Sentry reported a random error coming from Axios, `Error: timeout of 0ms exceeded`. Under what circumstances would this error appear? We don't have timeout settings configured, and 0ms seems like a mighty short time for any request to finish, so why is this error thrown? It appears to have been a one off that is not readily reproducible, so I can't provide test code, but the underlying network error seems to have been `ECONNABORTED`. Axios version 0.18.0
avoid writing the temporary file when evaluating the config file
Description I run vite inside a docker container for security reasons. My `docker run` looks like: [code block] As you can see, the application code files are read-only and they can't be changed from inside the docker container (for example, some mistake like `rm -rf *` can't remove all my code files). But since version 3.0.1, `vite build` creates the `vite.config.js.mjs` file in the root directory, and since version 3.0.3 it creates a file with a random name like `vite.config.js.timestamp-1659277944620.mjs`. Because my application root is the read-only, then `docker container exec -i "myApp" bash -l -c 'npm run build'` fails with error: [code block] Suggested solution Write file only to explicitly set directories. Alternative _No response_ Additional context _No response_ Validations - [X] Follow our Code of Conduct - [X] Read the Contributing Guidelines. - [X] Read the docs. - [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
Command-line completion?
I just wonder if there's a command completion like there is for the docker-compose command.
NextJS - Error: construction of webhook event returned an error: No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe? https://github.com/stripe/stripe-node#webhook-signing
Hi I am pulling my hair out trying to pass raw JSON to NextJS 12 endpoint. I have tried sooo many solutions and I just cant get it to work. Please help as I have wasted half a day on this and I am at a loss. Create test webhook in stripe and passing in Secret Signing key from webhook test dashboard "whsec ..." I get a signature from the test webhook I trigger in the dashboard but I am constantly getting: Error: construction of webhook event returned an error: No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe? https://github.com/stripe/stripe-node#webhook-signing The code below is from Reddit, where some had a similar issue. I have tried all of these solutions here: https://github.com/vercel/next.js/discussions/13405 Seems to be an issue in a lot of forums. Please help. Exhausted! [code block]
Error in connector: Error creating a database connection. (Operation timed out (mobc timeout))
Bug description Sometimes, due to DB connections limit, the client fails with this error: [code block] my DB configuration is like so: `DATABASE_URL="mysql://someUser:somePass@host/db?connection_limit=10"` Note: `connection_limit` How to reproduce It happened to me when trying to create/update/delete several entities at the same time, for example: [code block] Expected behavior The client should be able to recover from a timeout connection. Environment & setup - OS: Ubuntu - Database: Mysql - Node.js version: 14 - Prisma version: 2.11.0
I set withCredentials is true, but cross-site requests failed. I can't find why...
the cross-site url is can access directly, but I can't get the data(dateType is json) through cross-site requests. Code: [code block]
Consider JSX-like syntax inside dart code
It would be great if aside from the current way of building widgets you could add JSX like capabilities. I mean add tiny syntactic sugar to enable XML like constructs inside dart code. It just makes code so much easier to read/develop/debug/maintain and also easier for powerful GUI builders to integrate with editable code. Looking for something like DSX: https://spark-heroku-dsx.herokuapp.com/index.html Carlos. --- The current issue with DSX is about proper integration with Flutter tools as to provide a great developer experience with debugger, auto-complete, etc. working on .dsx files. Telling users that they can use DSX but can't use debugger or enjoy auto-complete is a non starter for me. If anybody wants to help, what I need is to figure out a way to add full preprocessing support (with source map) to Dart Tools and VS Code Dart plug in. Once the tools support that DSX or any other transpiling language (any language that is a superset of Dart but compiles everything down to Dart) would just work. If you can and would like to help, let me know.
Support !important for styles?
We currently don't support `!important` as it has to be set using `style.setProperty(name, value, priority)`. This should be trivially easy to implement if it's something want to support, although I'm not sure about the performance implications (EDIT: #1886), although I can't imagine it would be measurable as we would be doing the string test ourselves and those are cheap. http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleDeclaration ~~OK... apparently IE8 doesn't support this _at all_, it might still be worth implementing, for the future and for those who don't care about IE8.~~ ~~After further experimentation, apparently it is! `style.setAttribute(name, value)` (priority is part of the value).~~ But apparently that was wrong as well, the only way to set it seems to be with `cssText`, an acceptable work-around may be to just use `cssText` when we detect an `!important` style, which should be seldom enough that performance is a non-issue. An important consideration is that we _already_ support this for the initial render, but subsequent updates will _fail_ as `!important` isn't recognized for properties.
Add support for Deno
Problem Not yet supported in Deno Suggested solution Add support for Deno It would be great to add support for Deno I'm not sure is it possible right now or in the future but seeing how Deno gaining momentum it will be a very near future.
Local Studio - Feature Request for Saving Snippets Locally
Bug report Describe the bug In the local studio dashboard, I cannot edit a SQL Query name To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. In the local studio, go to the SQL editor 2. Click "New query" 3. Do not edit the name, click elsewhere 4. Come back, you can no longer edit the name and it says "Untitled query" Expected behavior I should be able to edit the query name Screenshots System information - OS: mac - Browser (if applies): Brave - Version of supabase-js: @supabase/supabase-js": "^2.36.0 - Version of Node.js: v20.5.1 Additional context Add any other context about the problem here.
Implement private fields proposal
I think it would be nice to have the stage 1 private fields proposal implemented in TypeScript. It'll mostly supercede the current pseudo-private implementation, and a fully-correct implementation is only transpliable to ES6 using per-class WeakMaps. I'll note that the spec itself uses WeakMaps internally to model the private state, which may help in implementing the proposal. Currently, the proposal only includes private _properties_, but methods are likely to follow. Also, the most important part of the proposal is that private properties are only available within the class itself.
Add support for opening multiple project folders in same window
Right now it doesn't seem possible to opening multiple project folders in the same window which imho is a bit constraining. If you are working on modular modern projects it's a must have to be productive.