All Issues
24,993 verified issues
Not scroll to top after changing route
What version of Next.js are you using? 11.1.2 What version of Node.js are you using? v15.9.0 What browser are you using? Chrome What operating system are you using? macOS How are you deploying your application? next start Describe the Bug I have two pages, each one contains lazy render components. After changing route by clicking <Link scroll={true}>. The page doesn't scroll to top. This happens on Chrome IOS (work well on safari IOS) Expected Behavior It should scroll to top after changing page To Reproduce I have created a demo project here: https://github.com/TanDung2512/demo-bug-scroll-nextjs 1. Accessing website on Chrome by an Iphone. 2. Scroll till the page renders more sections. 3. Click any item to change page https://user-images.githubusercontent.com/36843017/132081810-87d47392-4756-4a76-9500-2dc093b78262.MP4 <sub>NEXT-1347</sub>
EC2 permissions for VPC not set on first deploy
Hi Guys, I have multiple serverless projects up and running, but today I wanted to set up a new one, and I can't figured it out. My project is inside a VPC, and I have a permission error on the "AWS::Lambda::Function" role: > Your access has been denied by EC2, please make sure your function execution role have permission to CreateNetworkInterface. EC2 Error Code: UnauthorizedOperation. EC2 Error Message: You are not authorized to perform this operation. But my serverless.yml is setup the same way than my working projects: [code block] As you can see, I clearly set the iamRoleStatements for EC2. Moreover, I read this in the documentation: > Further, if you have specified VPC security groups and subnets for your lambdas to use then the EC2 rights necessary to attach to the VPC via an ENI will be added into the default IAM policy. But when the role is created, the inline policy attached is the following: [code block] No rights about EC2 are added... Does anyone have an idea? Many thanks
Interpolate environment variables in docker-compose.yml
(I'm creating a fresh issue for this as the old one has accumulated rather a lot of baggage.) It should be possible to pass in environment variables to the value of any\ configuration entry in `docker-compose.yml`. A lot of people want to do it, it's good for portability and I'm satisfied it's not going to cause chaos. I have some reckons. Required variables and optional defaults It's useful to be able to specify that a variable that _must_ be present in the environment, i.e. that Compose will refuse to run if it isn't. However, this will be a pain when you've got lots of them, so it should either be something you explicitly enable, or it should be possible to specify a default value. The MVP implementation does not need to have either feature, but there should be a clear path to implementing both in a backwards-compatible way. Syntax There's a strong case for implementing an established standard, as long as it's not heavyweight - our requirements for functionality are minimal. - POSIX parameter expansion is OK. It has a few too many features, but we could implement a subset of them: - `${VARIABLE}` - outputs empty string if `VARIABLE` is unset - `${VARIABLE-default}` - outputs `default` if `VARIABLE` is unset - `${VARIABLE?}` - errors out if `VARIABLE` is unset https://github.com/docker/compose/pull/845 implemented a Bash-style `${VARIABLE:default}` syntax, which is similar to POSIX parameter expansion but slightly different. - Python's format syntax woul
Angular ServiceWorker interferes with Firestore's network requests ("Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds" log warning).
[REQUIRED] Describe your environment Operating System version: MacOS 10.13.4 Firebase SDK version: 5.0.4 * Firebase Product: Firestore [REQUIRED] Describe the problem Firestore fails on production mode. > [2018-06-04T06:11:47.859Z] @firebase/firestore: Firestore (5.0.4): Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds. >This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend. Steps to reproduce: build project using [code block] and served in firebase hosting [code block] Relevant Code: Firestore fails to start. [code block] >undefined -> console.log(data) The version used is `firebase: "5.0.4"` with `angularfire2: "^5.0.0-rc.10"`
[Packager] doesn't resolve modules that are symlinks
As described in the browserify handbook you can use symlinks in the `node_modules` folder to reference modules. This is mainly useful for preventing `../../../../` requires. With a symlink setup from the project root setup like: `ln -s src/app node_modules/app` in any file in the project you can: [code block] However, the packager can't resolve them: `Requiring unkonwn module "app"`. Edit: Check out this repo to easily reproduce the error above: https://github.com/JaapRood/react-native-packager-symlink-bug
How to use stream: true?
I'm a bit lost as to how to actually use `stream: true` in this library. Example incorrect syntax: [code block]
JSX {" "} spaces
Is there any way at all to stop Prettier adding these horribly ugly spaces? Perhaps just _not_ format strings like this if it needs to add spaces like this. Prettier 1.11.1 Playground link Input: [code block] Output: [code block]
A proposal for a mock module for ioredis
mranney/node_redis has many mock libraries that help us to write unit tests without actually starting a Redis server. Examples are: https://github.com/faeldt/redis-mock https://github.com/hdachev/fakeredis Any plan to provide a mock interface?
AWS ELB serves wrong SSL certificate after adding second custom domain
An AWS Application Load Balancer (or Elastic Beanstalk-managed ALB) is configured with one SSL certificate. After adding a second custom domain to the same application, HTTPS connections from the second domain get the wrong certificate (the first domain's cert), causing SSL mismatch errors in browsers. The issue is that the ELB HTTPS listener must have a certificate explicitly added for every domain it serves — it does not auto-detect from DNS.
Can not send cookie back from client, tried many ways
Summary I'm new user from nodejs (expressjs) and axios too and I have a problem. I set cookie from nodejs server with: [code block] [code block] I can see response cookie from browser but in storage I can not see. I use res.header do the same, nothing happen. httpOnly: false does not work. And in client I try: [code block] I can not find other ways to do this, every result I got in google do this but I dont know why that not working for me. With Postman it automatic send cookie every request. Please help me! Environment - API: http://localhost:5000 - Front end: http://localhost:2000 - Axios Version: 0.27.2 - Browser: Chrome 101.0.4951.64 (Official Build) (64-bit) - Node.js Version: v12.13.0 - OS: Ubuntu 20.4 - Additional Library Versions: Reactjs 17.0.2
[FIXED] Android build failures `No matching variant of com.facebook.react:react-native:0.71.0-rc.0 was found.`
Description Hey all, I'd like to share an update on a series of build failures React Native & Expo users have been experiencing when building Android apps starting from November 4th 2022. We'd like to apologize for the disruption this caused to your developer workflows. The React team is fully committed to delivering a smooth developer experience, and we take this type of issues extremely seriously. 📢 Patches for >= 0.63 We have prepared releases for all the main versions of react-native with an hotfix: 🛳 0.70.5: https://github.com/facebook/react-native/releases/tag/v0.70.5 🛳️ 0.69.7: https://github.com/facebook/react-native/releases/tag/v0.69.7 🛳 0.68.5: https://github.com/facebook/react-native/releases/tag/v0.68.5 🛳️ 0.67.5: https://github.com/facebook/react-native/releases/tag/v0.67.5 🛳️ 0.66.5: https://github.com/facebook/react-native/releases/tag/v0.66.5 🛳️ 0.65.3: https://github.com/facebook/react-native/releases/tag/v0.65.3 🛳️ 0.64.4: https://github.com/facebook/react-native/releases/tag/v0.64.4 🛳️ 0.63.5: https://github.com/facebook/react-native/releases/tag/v0.63.5 By updating to these patch versions, your Android build should start working again. To do so, in your `package.json` change `react-native`'s version to the relevant new patch (ex. if you are on 0.64.3, change to 0.64.4) and run `yarn install`. No other changes should be necessary, but you might want to clean your android artifacts with a `cd android && ./gradlew clean` before trying to re-r
[BUG]: migrations do not work - table already exists - ER_TABLE_EXISTS_ERROR - mysql
What version of `drizzle-orm` are you using? 0.30.10 What version of `drizzle-kit` are you using? 0.20.18 Describe the Bug whenever I run my package.json script: `"db:migrate": "bun run db/migrate.js",` my `migrate.js`: [code block] I get [code block] Expected behavior According to documentation the migrations should be skipped if these were already applied, this does not seem to be happening. ref: https://orm.drizzle.team/docs/migrations [code block] my migrations should be able to run and apply new changes to the schema without complaining about table already existing. I am very keen on solution to this bug and or workaround if such exists. Environment & setup _No response_
[NEXT-1119] Socket.IO Not working anymore from Next.js 13.2.5-canary.27 to latest Next.js 13.4.1
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) App directory (appDir: true) Link to the code that reproduces this issue https://codesandbox.io/p/sandbox/nextjs-socketio-u89y82?file=%2Fpackage.json&selection=%5B%7B%22endColumn%22%3A1%2C%22endLineNumber%22%3A4%2C%22startColumn%22%3A1%2C%22startLineNumber%22%3A4%7D%5D To Reproduce Agenda of this project? - To setup the Socket.Io server and share the information from one client to another user socket.io events The App is have the following things - - An api for initialising the Socket.Io server - inside /pages/api/socketio - A client page to connect to this server - inside /app/page Whats the Issue? - There has been an unknown error in network connection from client side when its trying to create the Socket.Io connection. Since when this issue is happening? - This has been happening from Next.js version 13.2.5-canary.27 version and its still happening even in latest canary release 13.4.1-canary.2 and also the latest release Next.js 13.4.1 Do we have an Example project? - Yes, I have created a testing project in codesandbox, that I have already shared. (Link) Steps to Reproduce - Just see the console and network tabs for the client connection error. It will happen to all the versions on and above 13.2.5-canary.27 - And to see if its fixed, you need to downgra
macOS dock icon is miniscule
If you zoom way, way in you can see that it's in between VirtualBox and Activity Monitor: <img width="1134" alt="screen shot 2018-11-03 at 3 43 10 pm" src="https://user-images.githubusercontent.com/226872/48451437-488e6100-e75f-11e8-9953-0cf57e38fb8c.png"> - VSCode Version: Version 1.30.0-insider (1.30.0-insider) c72cb129f2a0b8117c9b01f3767026041d7d1d31 - OS Version: macOS 10.14. Steps to Reproduce: 1. Launch VSCode. 2. Observe the dock icon. Does this issue occur when all extensions are disabled?: Yes
[BUG] npm ci can't resolve dependencies without --force, or --legacy-peer-deps
Is there an existing issue for this? - [X] I have searched the existing issues This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior I've updated to latest node version which use npm 8.11.0, but the problem exist with versions >= 8.6.0 up to 8.12.1 when I do an `npm install --legacy-peer-deps`, all dependencies are correctly installed and I can start my app. but when my CI try do make an `npm ci`, I have conflit errors [code block] Expected Behavior I should not have any errors when I do `npm ci` since it should use package-lock wich contains all conflict resolutions. If I revert to npm@8.5.5, it works correctly without having to do a new `npm install` Steps To Reproduce [code block] you can also try without --package-lock-only but by removing `node_modules` folder Environment - npm: 8.11.0 - Node.js: 6.15.1 - OS Name: Alpine - System Model Name: WSL - npm config: [code block]
vite build error: out of memory
NOTE - PLEASE READ This issue has affected a number of people. Please do not comment with comments along the lines of "I'm also hitting this", but add a thumbs up to the issue instead. We know this is an important issue and "me too" comments will only drown out the comments from people attempting to resolve this issue and will be hidden. Please note however that Vite is a community driven project and a fix may need to come from the community For tips on working around the issue, please see https://rollupjs.org/guide/en/#error-javascript-heap-out-of-memory Describe the bug vite build error: out of memory. Reproduction https://github.com/Axeldeblen/realworld-big-build Possible improvements Reduce magic string memory usage when building source maps: https://github.com/Rich-Harris/magic-string/pull/161#issuecomment-607480189 Logs (Optional if provided reproduction) <--- JS stacktrace ---> ==== JS stack trace ========================================= 0: ExitFrame [pc: 00007FF69790ABBD] Security context: 0x01e6a86408d1 1: decode(aka decode) [000002AD02F874D1] [E:\vite-template\node_modules_rollup@2.40.0@rollup\dist\shared\rollup.js:~133] pc=0000039464A55451 2: decodedSourcemap(aka decodedSourcemap) [000002AD02F8A979] [E:\vite-template\node_modules_rollup@2.40.0@rollup\dist\shared\roll... FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 00007FF696CD180F napi_wrap+119407 2: 00007FF696C787E6 v8::internal::OrderedH
Types are not installed
Describe the bug Types for `socket.io-parser` and `engine.io-parser` are not installed To Reproduce Socket.IO server version: `4.5.4` When compile with typescript it throws these errors: [code block] Did I do something wrong? Do I have to install the types manually?
[BUG]: Extremely slow intellisense depending on schema size and amount
What version of `drizzle-orm` are you using? 0.27.0 What version of `drizzle-kit` are you using? 0.19.1 Describe the Bug Intellisense gets unusably slow when providing the schema in the `drizzle(sql, { schema })` instantiation. The intellisense delay depends on the schema amount size, it approaches 8 seconds for us on a Macbook Pro M2 Max with 40 tables, with other, non Macbook M processor people are reporting 10-15 second delays. It gets faster again when we only provide a subset of the schemas. Expected behavior Instant/fast intellisense. I suppose the TS types are calculated on the go when intellisense activates? This might be the bottleneck. Other libraries generate types and store them on the filesystem. Is this an option for Drizzle? Environment & setup Macbook Pro M2 Max
Unhelpful warning for `act` for react-dom@16.8
*Do you want to request a feature or report a bug? Feature/Improvement What is the current behavior? If there is test code that should be wrapped in `act(...)` then the current warning is given: [code block] When upgrading a large code base, this is basically useless. What is the expected behavior? Provide at least the test name if not the line number of code that triggered the warning. Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?* react@16.8.0 react-dom@16.8.0
[vulnerabilities][high] jsonwebtoken has insecure input validation in jwt.verify function
New jsonwebtoken vulnerability has been published. https://github.com/advisories/GHSA-27h2-hvpr-p74q