All Issues
24,993 verified issues
Server side locale always default in dynamic routes when a middleware is present
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) Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link) Link to the code that reproduces this issue or a replay of the bug https://github.com/XavierLasierra/next-dynamic-routes-bug To Reproduce 1. Clone repository, install dependencies and start the server 2. Go to the main page with a locale other than the default (ex `/en`) 3. Navigate to a dynamic route using `next/link` 4. The locale on the server side will be always the default one only when doing client navigation Describe the Bug When doing client side navigation to a dynamic route having a `middleware.js` file, the locale will always be the default one. [code block]` - This is not happening for static routes. - This is not happening for dynamic routes with no `middleware.js` file. Expected Behavior The locale will be consistent in dynamic routes. Which browser are you using? (if relevant) Chrome 115.0.5790.170 How are you deploying your application? (if relevant) _No response_
Compose error "HTTP request took too long to complete"
Lately I've been noticing the following error message quite frequently with `docker-compose up`: [code block] Increasing the `COMPOSE_HTTP_TIMEOUT` only seems to delay the error. Is this a known issue and/or is there a workaround for this? I'm using ubuntu 16.04, please find below the output of `docker-compose version` and `docker version`. I'd also like to note that I see this issue with docker for mac beta, docker-machine, etc. [code block] [code block]
HTTP API Support
Support HTTP API: https://aws.amazon.com/blogs/compute/announcing-http-apis-for-amazon-api-gateway/ --- Proposal of a configuration schema within a Serverless Framework _Note: This proposal is "live" (updated in place whenever there's an agreement on changes to it)_ [code block] In addition support for importing Open API objects can be added as: [code block] Implementation roadmap Implement and publish HTTP API support in following stages: 1. [x] Basic routes support, no cors, no authorizers, no open API objects import (#7274, #7331 & #7383) 1. [x] CORS support (#7336) 1. [x] JWT authorizers support (#7346) 1. [x] Access logs (#7385) 1. [x] Support existing HTTP API's (#7396) 1. [x] Support `timeout` setting (#7401) 1. [ ] (eventually) Open API object support - possibly leave out for community to implement (when demand shows)
Cannot use `terraform import` with module that has dynamic provider configuration
Terraform Version `Terraform v0.9.1` Affected Resource(s) N/A Terraform Configuration Files [code block] Debug Output https://gist.github.com/ff54870fee49636209ecfaa5de272175 Panic Output N/A Expected Behavior Resource was imported Actual Behavior [code block] Steps to Reproduce 1. `terraform import module.module_us_west_1.aws_cloudwatch_log_group.rds_os "arn:aws:logs:us-west-1:FILTERED:log-group:RDSOSMetrics:*"` Important Factoids N/A References N/A
Geolocation 'enableHighAccuracy' on Android always times out
Developing an Android app, whilst debugging on my Android Device running on 6.1, the geolocation api always returns an error callback with the message `Location request timed out`. [code block] If I toggle enableHighAccuracy option to false, the api works fine. In high accuracy mode, the timeout always takes as long as I specify in the timeout option i.e. 20 seconds. I've tried running with dev mode turned off. Should high accuracy mode work in Android?
Partial classes
Add support of partial classes. Mixins is not the same, because it's run-time realization. Need compile realization, where partial classes will be combine into one before converting typescript to javascript. [code block] will be: [code block]
Tracking issue for AWS CLI v2
Version 1.0.0 of the AWS CLI was tagged just over 5 years ago. In that time, a lot has changed. We've received tons of feedback from customers. We've learned what features customers enjoy, and what parts of the CLI we'd like to change. There are changes we've wanted to make, but needed to wait until the next major version of the AWS CLI due to either the backwards incompatible nature or the large scope of the change. Well, we're here now. This issue is to track all the work for CLI v2. We wanted to do this work on GitHub right from the beginning. Even though we're in the early stages of development, community feedback will play an important role in its development. Any AWS CLI v2 related issue/PR will be labeled with v2. We'll also reference this issue for any AWS CLI v2 related PRs so everyone can see all the changes we're making. * All the development work will be in the v2 branch. If you have an idea for CLI v2, whether it's a new feature or a change we couldn't make in v1 of the AWS CLI, please feel free to open a GitHub issue and let us know. You can also go through any issue labeled as CLI v2 and +1 features that you'd like to see us implement. Blog: https://aws.amazon.com/blogs/developer/aws-cli-v2-development/
Unable to send formData in axios (react-native android)
I am making a POST request to "Cloudinary" server to upload an image and sending formdata using axios in react-native. The whole process is working fine on iOS but on android i am getting "Network Error". I am using axios 0.18.0 and stuck on this from last 3 days. Someone please help me. This issue has been faced by many people but there is no solution so far. My code: ` var photo = { uri: image.sourceURL, type: image.mime, name: image.filename, }; var formData = new FormData(); formData.append('file',photo); formData.append('upload_preset','abcde'); axios({ url:'https://api.cloudinary.com/v1_1/abcde/upload', method:'POST', headers:{ 'Content-Type':'application/x-www-form-urlencoded' }, data:formData }).then(function(response){ }).catch((error) =>{ //Network error comes in }); `
Multiple files for --ignore-path
I use the --ignore-path argument and point it to an exhaustive `.gitignore` file. It's great that I don't have to duplicate the list of ignored files. However, there are a couple of files I'd like to exclude from prettifying but still want to commit. Is there any way to specify an additonal `.prettierignore` file so that I can add files without copying the entire `.gitignore`?
Xcode 12.5 troubleshooting guide (RN 0.61/0.62/0.63/0.64)
Hey folks. This issue wants to be a follow up to https://github.com/facebook/react-native/issues/31179; that issue has become really long so opening a new one to try and reduce the noise and confusion around it. Here is how to fix the Xcode 12.5 iOS build breaks with errors related to "atomic_wait_until is unavailable" (and similar messages). (sidenote: make sure you are using cocoapods 1.10.x) If you are on 0.61 Note well: this has only been tested by a few members of the community, not by me, so I can't ensure it will work. If you are still using RN 0.61, you can refer to this comment https://github.com/facebook/react-native/issues/28405#issuecomment-840914650 from @edgarbonillag. If you are on 0.62 1. add this line to your podfile (or modify it if you already had it): [code block] 2. change your package.json react-native dependency to [code block] 3. do all the classic necessary cleans (node_modules, caches, pod folders, etc)(react-native-clean-project is your ally) then do `yarn install` and a `pod install --repo-update` (if pod install fails on an error about a Flipper package, just remove the relevant lines from the podfile.lock and run the pod install again) If you are on 0.63 Note well: you need to be on latest 0.63.x release, at the time of writing 0.63.3. If you are on 0.63, you are in luck! You just need to add this line to your podfile (or modify it if you already had it): [code block] Then properly clean your caches (react-native-clean-project is you
[Question] Get 403 ERR when trying to download packages
Hi :), When we try to deploy our app (not behind a proxy), we get a 403 ERR from npm js. Everything was alright before this morning and no big changes happened. Is someone get this issue before? Step 9/14 : RUN npm install 403 Forbidden - GET https://registry.npmjs.org/@material-ui%2fcore EDIT: when we do it behind a proxy it works... Do you think npm js could have ban our server address
npm stuck too long on apple new m1 computer
Current Behavior: Stuck at "reify:rxjs: timing reifyNode:node_modules/@vue/cli/node_modules/typescript Completed in 3254ms"! No any feedback! <img width="978" alt="image" src="https://user-images.githubusercontent.com/14059031/101638252-cb7e6480-3a68-11eb-8a86-40aae874cd96.png"> Expected Behavior: install successfully! Steps To Reproduce: npm install -g @vue/cli Environment: - OS: macOS big sur 11.0.1 - Node: 15.3.0 - npm: 7.1.1
onUploadProgress will be 100% before uploading process finished
Describe the issue hey every body. in the first, sorry for my poor english language. i wrote some code for uploading some images and data together by formdata format in react-native. and i use node.js in backend side and every thing is ok. i can upload images. but problem has occurred when i want use `onUploadProgress`. then `loaded` parameter will be `100%` immediately but the upload process take some minutes after that. just in record when i use ajax in js code it's will be perfect so the problem is not from backend side. and it occurred just in react-native and the images select and crop by `react-native-image-crop-picker`. here is my code: Example Code [code block] Expected behavior, if applicable Environment - Axios Version 0.21.0 - Node.js Version v14.15.1 - OS: ubuntu 18.04 - Additional Library Versions React Native 0.63.0 Additional context/Screenshots
pgvector brew formula installs for PostgreSQL 17 but project uses PostgreSQL 16
Running `brew install pgvector` installs the extension compiled for the latest PostgreSQL version. If your project uses PostgreSQL 16 (which is common when postgres@16 is pinned), the vector.control and vector.dylib files are placed in the PostgreSQL 17 extension directory, not PostgreSQL 16's. Running `CREATE EXTENSION vector` fails with 'could not open extension control file' even after pgvector is installed.
progress bar UI for s3 copying
So I can have an idea how my transfer is doing please
[0.75.x/0.76.x] Failing to build on Windows - Could not move temporary workspace - Error resolving plugin [id: 'com.facebook.react.settings'] - java.io.UncheckedIOException
IMPORTANT: The latest official update on this issue is here https://github.com/facebook/react-native/issues/46210#issuecomment-2586892665 [code block] This is the full error. The command I've used to create the project is `npx @react-native-community/cli init TodoApp2 --directory ./native-cli-todo-app-2`. The projects is created successfully. After I run `npm run start` and hit `a`, for android, build fails showing the above error. Another project which uses 0.74.3 is working just fine. Creating new project automatically uses 0.75.2 version which is fine, but it shows the error while building because of which development server doesn't start.
[BUG] "sill idealTree buildDeps" takes a lot of time a project with workspaces
Is there an existing issue for this? - [X] I have searched the existing issues Current Behavior After executing `npm install` the `sill idealTree buildDeps` step takes a long time (minutes) causing npm@7 working with workspaces slower than npm@6 installing projects separately. It seems that is fetching packages sequentially instead using parallelization. Vídeo with the demo: https://user-images.githubusercontent.com/1561955/118666331-61c26d80-b7f3-11eb-8060-4cb7d28480a9.mp4 Expected Behavior `npm install` on npm@7 with workspaces takes less time than npm@6 installing manually each workspace. Steps To Reproduce 1. In a environment with a lot of dependencies and workspaces. 2. With this config: [code block] 3. Run `npm install` 4. See that the step `buildDeps` take longer than expected. Some considerations: - We're using some npm private packages on our package.json. - Workspaces are dependencies of root project as well. More info: On Travis, builds using npm@6 and installing workspaces manually takes 90s. Using npm@7 it takes 170s using a single npm install. Environment - OS: macOS 11.3.1 - Node: 16.1.0 - npm: 7.17.0
Importing CSS files?
Sometimes it's nice to break out your CSS into a separate `.css` file. I've tried to do the following: [code block] Then in the index.js, I've tried to do: [code block] And in next.config.js: [code block] But unfortunately, it keeps giving me: [code block] Seems like it's not resolving to the right place for some reason, the local `component.js` works though via `import component from './component.js'`, so I'm not sure what's going on here.
[BUG] npx fails with "could not find executable" when running husky in v7
The latest version of `husky` is broken in npm v7. I'm not sure if this regression is intended or not, i.e. if Husky needs to be updated or npm needs a bugfix. Current Behavior: [code block] Expected Behavior: [code block] Steps To Reproduce: 1. Create a new empty folder and run `npm init -y` inside it 2. Install `husky` with `npm i -D husky` 3. Create a simple config, e.g . `echo '{ "hooks": { "pre-commit": "echo Hello World!" } }' > .huskyrc.json` 4. Run `npx husky-run pre-commit` 5. npm v7 will fail with "could not determine executable", while npm v6 works Environment: - OS: Ubuntu 20.04 or Windows 10 v2004 - Node: 14.10.1 - npm: 7.0.0-beta.11
depends_on cannot be used in a module
Hi there, Terraform Version 0.8.0 rc1+ Affected Resource(s) module Terraform Configuration Files [code block] Debug Output Error loading Terraform: module root: module legacy_site: depends_on is not a valid parameter module root: module legacy_site: depends_on is not a valid parameter Expected Behavior I am trying to use the new depends_on instead of the above outputs, so I create and provision my app once I know database and caches are built. Actual Behavior Nothing as terraform errors out as above. Steps to Reproduce 1. `terraform apply` References depends_on can reference modules. This allows a resource or output to depend on everything within a module. (#10076)