All Issues
24,993 verified issues
Minified React Errors in production
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 or a replay of the bug https://github.com/gaurishhs/Portfolio To Reproduce [code block] Describe the Bug I'm using `next-themes` along with app directory and i get these Minified react errors in the production deployment only on Vercel. These errors are not there during development mode or if i use `vc deploy` Expected Behavior No such errors Which browser are you using? (if relevant) Brave Browser How are you deploying your application? (if relevant) Vercel
Next 13 + experimental app dir + Tailwind hot-reload of classes doesn't work
Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information ❯ npx next info Operating System: Platform: darwin Arch: x64 Version: Darwin Kernel Version 21.6.0: Thu Sep 29 20:12:57 PDT 2022; root:xnu-8020.240.7~1/RELEASE_X86_64 Binaries: Node: 16.16.0 npm: 8.11.0 Yarn: 2.4.3 pnpm: N/A Relevant packages: next: 13.0.7-canary.3 eslint-config-next: 13.0.3 react: 18.2.0 react-dom: 18.2.0 Which area(s) of Next.js are affected? (leave empty if unsure) _No response_ Link to the code that reproduces this issue https://github.com/vercel/app-playground To Reproduce - Grab latest version of Next.js with experimental app dir enabled (I'm using the playground example) - Load project, go to `/streaming` - In your editor, go to `Product.tsx` and edit a class with a width class `w-*` (go to line 75) - Swap `w-1/3` for `w-6/12` save and wait for hot-reload (don't manually refresh the page) - You won't see your new class applied, element will break due to class not being applied - Go back to editor and try now `w-10/12`, wait for hot-reload. Same result as above. - Set it now to `w-6/12` and manually reload, you will see your class now (and it seems to be caching this class now) - If you repeat the steps above `w-6/12` won't fail anymore because it seems to be cached now somehow Describe the Bug Hot reloading of Tailwind CSS when you chan
GitHub Actions OIDC token request fails with status 500 intermittently
GitHub Actions workflows using OIDC (OpenID Connect) for keyless AWS authentication fail intermittently with 'Unable to get OIDC token: Error: Request to OIDC provider failed with status 500'. The failure is not deterministic — the same workflow passes on retry without code changes. The issue is on GitHub's OIDC provider infrastructure and is a transient service reliability problem.
Feature request: Basepath support
Feature request Is your feature request related to a problem? Please describe. Multi zones is a great feature which allows to run multiple next.js apps on the same domain, but it doesn't allow to define a basepath which will be accepted by all parts of next.js. Since we are not able to namespace apps right now it is not possible to have the same names for pages in various apps. Describe the solution you'd like I want to be able to configure a `basepath` in the next.config.js file. Thanks to this configuration all parts of next.js (Router, Link, Static assets etc.) will be aware of the basepath and will automatically generate and match to the correct paths. Describe alternatives you've considered One alternative is to nest all desired pages into a folder which matches the basepath. This solves just one small issue with routing and is quite ugly because most of the my basepaths are not one level paths. The second alterantive is to configure a proxy in a way where the basepath is automatically removed before the request arrives into a next.js app and also implement a custom Link component which automatically adds basepath to all links. I just don't want to maintain custom fork of next.js. It doesn't make sense in my opinion. Additional context The `assetPrefix` solution allows us to define a different prefix for each app. But as fair as I know it works only with different hosts. with-zones example [code block] If I add a basepath to it everything fails [code block] <img wid
[1.0.0] TypeError: Cannot read properties of undefined (reading 'create')
Describe the bug [code block] To Reproduce [code block] Expected behavior Runs without error. Environment - Axios 1.0.0 - Node.js 18.10.0 - macOS Monterey 12.6 Additional context/Screenshots 0.27.2: runs without error 1.0.0: `TypeError: Cannot read properties of undefined (reading 'create')` (I could not see any breaking change)
Nested relations filtering doesn't work
Issue type: [ ] question [x] bug report [ ] feature request [ ] documentation issue TypeORM version: [ ] `latest` [ ] `@next` [x] `0.2.15` (or put your version here) Steps to reproduce or a small repository showing the problem: I have 2 models category.entity.ts [code block] post.entity.js [code block] When i filter query by category_id, everything is ok: [code block] But, filter works only by primary nested field. Filtering by other fields don't work: [code block] [code block] Are there options to implement this?
dns configuration option does not work on docker-compose==1.6.0
Step 1: [code block] Step 2: [code block] Step 3: [code block] As you can see, `dns` option is ignored by `docker-compose` and some garbage is set instead. This prevents my containers from starting up because they require to use mentioned DNS server. BTW, what kind of shit is 127.0.0.11, and how it get to resolve.conf? With version 1 of yaml file everything is working as expected (nameserver is set correctly).
Deploy many micro/nano services to one API Gateway
This is a Feature Proposal Description I'd like to deploy many microservices to one API Gateway, but currently I'm not able to as the template is creating a new Gateway for every service. Would it be possible to change the behaviour? I may create a Pull Request for this if you agree Topic on the forum: http://forum.serverless.com/t/multiple-services-behind-a-single-api-gateway/191
Consider SSE to enable server->client http subscriptions
Reading through the #532 PR it occurred to me that the JSON-RPC notification system only works one way, from client to server. Most of the time you want it to be from server to client. Although nothing about the spec says which side is which, in a browser this basically means the browser is the client. One interesting approach could be to use Server Sent Events. This would allow for stateless load balance-able subscriptions that could work with HTTP2. From what I'm seeing though I'm not sure if it would technically fall under a JSON-RPC complaint spec; though you probably can treat as a server to client notification. Nice thing is this is already built into browsers with polyfills available for node and most languages. I think you'd create/cancel as you do currently but the client would also fetch on a new route /subscription/3nxu4ex234. Know this is separate from the websocket implementation but SSE isn't a well known. The major downside of the SSE spec as it stands is the text only protocol (compared to binary for websockets) but in a JSON-RPC context the point is moot. <sub>TRP-63</sub>
Epic: "compose run" should support every "docker run" option
`fig run` should support every option of `docker run`, just referring to a service instead of an image. [code block] Todo (in rough priority order) - [x] `-u` https://github.com/docker/compose/pull/971 - [x] `--entrypoint` https://github.com/docker/compose/pull/511 - [x] `-w` https://github.com/docker/compose/pull/332 - [x] `-p` https://github.com/docker/compose/issues/1709 - [x] `-v` - [x] `--cpuset` - [x] `--memory` - [x] `--env-file` - [x] `--net` - [x] `--memory-swappiness` #2383 - [ ] `--volumes-from` #1769
Error: Entity metadata was not found
[code block] I have these 3 files and getting this error when I start my app. [code block] Not sure what to do, need some help on this.
IOS publish
react-native-cli: 2.0.1 react-native: 0.64.1 error when trying to publish to Apple Store Dear Developer, We identified one or more issues with a recent delivery for your app, "App" 1.0 (7). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in app: _isKeyDown, _modifiedInput, _modifierFlags, handleNotification:, isPassthrough, onSuccess:, removeValuesForKeys:completion:, setCategoryID:. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ Best regards, The App Store Team
Error: Cannot find module when deploying to heroku
Using latest next.js relase and a simple hello world index page with 0 dependencies fails to run on heroku with the following error: [code block]
Non-deterministic build
Describe the bug Executing builds multiple times with the same code generates different hashes. Reproduction https://github.com/ttionya/vite-non-deterministic-build-repro Steps to reproduce Clone the aforementioned repro, install dependencies, and execute `npm run build` multiple times. Verify the hash of the vendor file. System Info [code block] Used Package Manager npm Logs _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 reports the same bug to avoid creating a duplicate. - [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead. - [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. - [X] The provided reproduction is a minimal reproducible example of the bug.
[BUG] npm cache verify EMFILE
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 Currently observing EMFILE errors when running `npm cache verify` using npm >=8.6.0 on our Jenkins agents (EC2 instances), despite increasing `ulimit -n` from 1024 to 8192. Cannot reproduce in the same exact instance when using npm 8.5.5. Please let me know what detail might be useful to help debug this! I've collected strace output and silly-level logging. If any of that is useful, I can attempt to sanitize it to share! In the meantime, I'll likely move forward with removing the `npm cache verify` step from our Jenkins pipelines, and see if the other commands can succeed, although that will leave me with fewer warm fuzzies. [code block] [code block] Expected Behavior [code block] Steps To Reproduce 1. On our Jenkins build agents (see environment below) 2. With a particular .npm cache (I can try to make this available, upon request) 3. When using npm versions >= 8.6.0 4. Run `npm cache verify` 5. Observe EMFILE error Environment - npm: 8.6.0 and 8.7.0 - Node.js: 14.19.1 - OS Name: Amazon Linux 2 - System Model Name: - npm config: [code block] ``` $ cat /etc/*-release NAME="Amazon Linux" VERSION="2" ID="amzn" ID_LIKE="centos rhel fedora" VERSION_ID="2" PRETTY_NAME="Amazon Linux 2" ANSI_COLOR="0;33" CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2" HOME_URL="https://amazonlinux.com/" Amazon Linux relea
Explore encouraging users to not ship DEV mode to production
*Do you want to request a feature or report a bug? Feature What is the current behavior? Developers meaning to do the right thing will often accidentally ship DEV mode to production rather than PROD mode. This can have a significant impact on performance. Although DEV->PROD is a one line change, it's something React could explore encouraging. <img src='https://cloud.githubusercontent.com/assets/110953/21949283/b876d642-d9a5-11e6-9b52-83a6dc3fd750.jpg' width='400px'> <img src='https://cloud.githubusercontent.com/assets/110953/21949289/c283af0c-d9a5-11e6-8f05-d100cc0814f0.jpg' width='400px'> There's great nuance here and I know that there's balance to be struck between the overall DX value this brings vs UX. Another challenge is that the change itself is trivial to make. It's unclear whether the right solution here is better defaults or stronger advocacy. Folks like @sebmarkbage have been acknowledging that this is a known issue so perhaps there's room for discussion to help improve this. <img src='https://cloud.githubusercontent.com/assets/110953/21949384/b4a5b780-d9a6-11e6-917e-1b0d513e8867.jpg' width='400px'> He's also noted that a switch from no warnings to DEV may require some folks to fix whole codebases which is also suboptimal. There may be an in-between solution worth talking about here however. What is the expected behavior? React encourages users to ship PROD mode to production rather than DEV. I would be open to a solution that is either provided at the lib
resolve-url-loader cannot operate: CSS error when using @apply
I put the following in my `.scss` file: [code block] and after running webpack I can use the classes but I get the following error at the end of the build process: WARNING in ./node_modules/css-loader?{"url":true,"sourceMap":false,"importLoaders":1}!./node_modules/postcss-loader/lib?{"sourceMap":true,"ident":"postcss","plugins":[{"version":"6.0.13","plugins":[null,null,null,null,null,null,null,null,null],"postcssPlugin":"tailwind","postcssVersion":"6.0.13"},null,null]}!./node_modules/resolve-url-loader?{"sourceMap":true,"root":"/home/vagrant/gitlab/resources/statamic-site-template/public/site/themes/foundation/node_modules"}!./node_modules/sass-loader/lib/loader.js?{"precision":8,"outputStyle":"expanded","includePaths":["./node_modules/foundation-sites/scss/","./node_modules/font-awesome/scss/","./node_modules/motion-ui/","./node_modules/video.js/src/css/"],"sourceMap":true}!./sass/styles.scss (Emitted value instead of an instance of Error) resolve-url-loader cannot operate: CSS error /home/vagrant/gitlab/resources/statamic-site-template/public/site/themes/foundation/sass/styles.scss:6698:3: missing '}' at error (/home/vagrant/gitlab/resources/statamic-site-template/public/site/themes/foundation/node_modules/css/lib/parse/index.js:62:15) @ ./sass/styles.scss 4:14-245 @ multi ./node_modules/jquery/dist/jquery.min.js ./node_modules/what-input/dist/what-input.min.js ./node_modules/foundation-sites/dist/js/foundation.min.js ./node_modules/motion-ui/motion-ui.js ./node_
[BUG]: using `pgEnum` generates faulty sql migration
What version of `drizzle-orm` are you using? 0.26.1 What version of `drizzle-kit` are you using? 0.18.1 Describe the Bug Creating a user schema with role enum [code block] generates this sql migration [code block] which fails when running with error `PostgresError: type "role" does not exist` unless i wrap `Role` in double quotes manually like this [code block] Expected behavior Double quotes should be added automatically Environment & setup node v18.16.0
Terraform init is extremely slow
Terraform init takes forever and it seems like it is due to provider download. This extremely slow behaviour is consistent for the last 2 days. Working like that is hellish as I'm using terragrunt which runs the `terraform init` command often in my case. Drilling down on the trace logs, I've seen that the download of https://releases.hashicorp.com/terraform-provider-aws/3.22.0/terraform-provider-aws_3.22.0_darwin_amd64.zip takes usually 1-5 minutes minimum. When I simply download this url in my browser, it never takes more than 15 seconds....usually less than 10. When I run the `init` command with trace logs, it is almost always takes many many minutes to finish. I have no internet issues at ALL <img width="645" alt="Screen Shot 2020-12-29 at 2 55 49 PM" src="https://user-images.githubusercontent.com/3888998/103285144-f3b50f80-49e5-11eb-8aa2-87e77c589fe5.png"> Terraform Version [code block] Terraform Configuration Files I have created only one file in my example project, `backend.tf` and this is the its content [code block] Debug Output https://gist.github.com/AlmogCohen/b8af6e33c170c393a63e126226ad7108 Crash Output Not relevant Expected Behavior Terraform provider download should take as fast as it takes in the browser, and terraform init should not take 5 minutes for a very very simple terraform proejct Actual Behavior Terraform provider/plugin downloads takes forever Steps to Reproduce 1. `terraform init` Additional Context I'm using terragrunt, so the `init` comm
when i run-ios it run but then stop execution until i cross ❌ the terminal
Description info Opening the app on iOS... info Found Xcode workspace "FocusFlow.xcworkspace" info No booted devices or simulators found. Launching first available simulator... info Launching iPhone SE (3rd generation) (iOS 17.0) info Building (using "xcodebuild -workspace FocusFlow.xcworkspace -configuration Debug -scheme FocusFlow -destination id=A3B53EE6-A05D-49D6-8F89-819EFDC7921B") info 💡 Tip: Make sure that you have set up your development environment correctly, by running react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor Command line invocation: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace FocusFlow.xcworkspace -configuration Debug -scheme FocusFlow -destination id=A3B53EE6-A05D-49D6-8F89-819EFDC7921B User defaults from command line: IDEPackageSupportUseBuiltinSCM = YES Prepare packages ComputeTargetDependencyGraph note: Building targets in dependency order note: Target dependency graph (84 targets) Target 'FocusFlow' in project 'FocusFlow' ➜ Implicit dependency on target 'Pods-FocusFlow' in project 'Pods' via file 'Pods_FocusFlow.framework' in build phase 'Link Binary' ➜ Implicit dependency on target 'React-CoreModules' in project 'Pods' via options '-framework CoreModules' in build setting 'OTHER_LDFLAGS' ➜ Implicit dependency on target 'DoubleConversion' in project 'Pods' via options '-framew