All Issues
24,993 verified issues
Android build failed: 'Failed to list versions for com.facebook.react:react-native.'
Description What went wrong: Could not determine the dependencies of task ':app:compileDebugKotlin'. > Could not resolve all files for configuration ':app:debugRuntimeClasspath'. > Could not resolve com.facebook.react:react-native:+. Required by: project :app project :app > project :react-native-push-notification project :app > project :react-native-code-push project :app > project :react-native-async-storage_async-storage project :app > project :react-native-community_blur project :app > project :react-native-community_clipboard project :app > project :react-native-community_datetimepicker project :app > project :react-native-community_masked-view project :app > project :react-native-community_netinfo project :app > project :react-native-community_picker project :app > project :react-native-firebase_analytics project :app > project :react-native-firebase_app project :app > project :react-native-firebase_crashlytics project :app > project :sumsub_react-native-mobilesdk-module project :app > project :react-native-action-sheet project :app > project :react-native-appsflyer project :app > project :react-native-camera project :app > project :react-native-config project :app > project :react-native-device-info project :app > project :react-native-fbsdk-next project :app > project :reac
allow removing something in docker-compose.override.yml
My usecase is that the base `docker-compose.yml` maps a certain port in the `ports` section. In my `docker-compose.override.yml` I'd like to change that port since I already have a different service running there on my host. As far as I understand the current implementation it is only possible to add stuff, override extends the other file. As far as I can tell there is no way to remove an entry. And I can't think of an obvious syntax for it.
yarn install throw error because `oxide-node-api-shim` a non-existing file
_Maintainer's note: This issue has been fixed in v3.2.6._ --- Tailwind: `v3.2.5` Node: `v19.6.0` Yarn: `v1.22.19` When trying to install new Tailwind version `3.2.5` using Yarn, I get that error: `error Package "" refers to a non-existing file '"/Users/akoraie/MyApp/assets/oxide-node-api-shim"'.`
Login to Firebase does not work on Safari 16.1+
Describe your environment Operating System version: Mac OS 12.6 Browser version: Safari 16.1 Firebase SDK version: 9.10.0 Firebase Product: auth Describe the problem Steps to reproduce: Try logging in to a site using `signInWithRedirect`. Notably it redirects back to the site without an error, and does not log the user in. Checking `getRedirectResult` returns a null user. This seems like a severe issue as iOS 16.1 will be released next week and presumably this issue will affect all those iOS users. Notably there seems to be a workaround of using `signInWithPopup`. It seems to work for us, though it is unclear why. Relevant Code: [code block]
TextInput hangs with Samsung keyboard's Grammarly integration
UPDATE: we have now released patch releases containing fixes for: https://github.com/facebook/react-native/releases/tag/v0.69.10 https://github.com/facebook/react-native/releases/tag/v0.70.9 https://github.com/facebook/react-native/releases/tag/v0.71.7 https://github.com/facebook/react-native/releases/tag/v0.68.7 --- Description There is an issue with React Native's `TextInput` component when using Samsung's keyboard with the Grammarly integration enabled. When typing a text that is longer than a few lines, the app often hangs and becomes unresponsive, leading to a high rate of ANRs and crashes. This issue has already been documented here and here but I'm worried that the lack of a reliable reproducer as well as the noise due to other random freeze and crashes in Android (esp. with the new Android 13 update) is preventing those issues from gaining traction and becoming a high priority. I am therefore creating this new issue focused solely on the impact of the Samsung keyboard's Grammarly integration on the `TextInput` component, with a reliable reproducer, as I believe that something can be done at the `TextInput` level to address it. Here is everything we know so far: - Any React Native app that involves writing long text in a `TextInput` seem to be impacted. - The issue happens with the default Samsung keyboard with the Grammarly integration (aka "Suggest text corrections" aka "Writing assistant") enabled. This integration is now enabled by default with Samsung's
HMR error: Cannot access '...' before initialization
Describe the bug The error happens when I try to edit component, that 1. Wrap in `connect` function (redux) 2. Is inside dependency loop 3. There is another component inside dependency loop Seems weird, but it's not so rare case when project uses routers like UiRouter or Universal router I expect that component will be updated with HMR without errors or may be reload the page but not to throw an error Reproduction Repo: https://github.com/xSorc/test-vite-fast-refresh-loop-dependency To reproduce this error you need to open the project and try to edit `Component.tsx`. You will see an error System Info Output of `npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers`: [code block] Used package manager: Logs [code block] --- Before submitting the issue, please make sure you do the following - [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] Provide a description in this issue that describes the bug. - [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 https://github.com/vuejs/vue-next instead. - [x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
Add read-only mode
- VSCode Version: 0.10.11 - OS Version: Fedora 23, 64bit Details: - Please add read-only mode and its keyboard shortcut. - It should be a switch. When turned on, opening new files will be in read-only mode. - It should be persistent across restarts. This feature should be very useful for code reviewing. And I think it's not hard to implement. Thank you,
[Proposal] Prisma Client Extensions
Client Extensions Proposal Hey folks, we started designing this feature and we’re ready to share our proposal. Please let us know what you think! Design We aim to provide you with a type-safe way to extend your Prisma Client to support many new use-cases and also give a way to express your creativity. We plan to work on four extension layers which are `$result`, `$model`, `$client`, `$use`. Let’s consider the following model: [code block] Computed fields We have this database model but we want to “augment” it at runtime. We want to add fields to our query results, have them computed at runtime, and let our own types flow through. To do this, we use `$result` to extend the results: [code block] We just extended our `User` model results with a new field called `fullName`. To do that, we defined our field with `compute`, where we expressed our field dependencies and computation logic. [code block] Result extensions will never over-fetch. It means that we only compute if we are able to: [code block] Finally, you will be able to add fields to all your model results at once via a generic call using `$all` instead of a model name: [code block] Results are never computed ahead of time, but only on access for performance reasons. Model methods Extending the results is useful, but we would also love to store some custom logic on our models too… so that we can encapsulate repetitive logic, or business logic. To do this, we want to use the new `$model` extension capabil
Suggestion: collapse unchanged regions in diff
When viewing a diff (2 pane or inline) it would be useful to collapse the unchanged lines. This helps focus in on just the changes, especially when the changes are few an spread out.
Scroll restoration happens too early before the page gets rendered after hitting browser back button
- [x] I have searched the issues of this repository and believe that this is not a duplicate. After transiting from one page to another page via next `<Link />`, if user clicks the back button and the previous page has `getInitialProps` method that takes some time to finish, the scroll position of the previous will be restored before the previous pages gets rendered. Demo source code can be found here After clicking back button, the "go back" text should still be visible (not scroll down to previous position) until the previous page gets rendered
Add functionality for allow self-hosted runner to protect workflow file and allow only execution only for collaborators for PRS
Description: Hi all, first of all I really like the github action runner and self-hosted runner. It has however an issue with working for `pull-request` workflows. I think the runner should have a way to be configurable to run only on Pull-requests from collaborator of X org or Repo. The problem to be solved is to protect the github-workflow file and don't be changed by any arbitrary PR ( so there is no output redirection or other code executed) it is a recurring topic in some forums, but there is no solution or any issue about this afaik. let me know, and ping me for any info . best
Xcode 14.3 - Error: Unable to resolve module ./Libraries/Components/DatePicker/DatePickerIOS
This issue is now fixed, for more details check out this comment. Description Since upgrading to Xcode 14.3 and working around the other new issues i.e. the codegen ios target version issue, there is still a further issue with metro. Getting a lot of these type of errors. It seems to be every time metro logs a log line from iOS (not Android), it then logs the below message as well (full paths redacted). This seems to cause a memory leak as well, with the metro node process eventually crashing when > 4GB RAM is used. The error message is interesting for many reasons. 1. Firstly it seems to be trying to resolve a flow type import. 2. Secondly the path does exist, but metro is not checking the platform-specific path i.e. `DatePickerIOS.ios.js`. 3. Thirdly we don't even use `DatePickerIOS` in the app. [code block] NOTE that this is not the codegen ios target version issue, I've already worked around that using the patch which has been released as 0.70.8 React Native Version 0.70.6 Output of `npx react-native info` [code block] Steps to reproduce Running a previously working app on Xcode 14.3 / iOS simulator with rosetta Snack, code example, screenshot, or link to a repository Can't provide one at this stage
docker-compose dry run
Would like insight to what docker-compose generates/executes
[NEXT-684] Fast-refresh for CSS files is not working in Firefox
Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information [code block] What browser are you using? (if relevant) _No response_ How are you deploying your application? (if relevant) _No response_ Describe the Bug So I just started a new next.js app using the `v13.0.5` with the experimental `app` folder. I noticed that CSS changes are not correctly updated in the browser. The browser is notified of the change, but the styles are not applied - if I manually refresh the browser I can see the correct styles. I also tried the canary version and the error still exists. Moving to `v13.0.4` seems to work fine. And I also tried with Tailwind following the beta documentation and also it doesn't work. Expected Behavior Updating styles should fast refresh and update the page with the new styles. Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster https://stackblitz.com/edit/vercel-next-js-viybne?file=app/global.css To Reproduce Open the `global.css` file, change the colors and save the file. You can see it working with the 13.0.4: https://stackblitz.com/edit/vercel-next-js-6sncvk?file=app/global.css <sub>NEXT-684</sub>
Unable to deploy single lambda function for version 1.52.1
sls deploy -f "function_name" is not working throwing and exception My serverless version is: Framework Core: 1.52.1 Plugin: 3.0.0 SDK: 2.1.1 `sls deploy -f function_name` is not working it throws and errors the complete trackback would be `TypeError: Cannot read property 'artifact' of undefined at ServerlessPythonRequirements.BbPromise.bind.then.then.then (/home/mahesh/shuttle/H2OLambda/pythonh20lambda/node_modules/serverless-python-requirements/index.js:176:48) ` Any update on this would be appreciated. Thank you
Suggestion: Range as Number type
When defining a type one can specify multiple numbers separated by `|`. [code block] Allow to specify number types as ranges, instead of listing each number: [code block] Maybe use `..` for integers and `...` for floats. [code block]
Nested ternary formatting - add indents back
Edit: I will no longer be actively participating in this thread - my reasons are explained in comment below. Hello, there are many - including me thinking that change to nested ternary is not best decision. Eg threads https://github.com/prettier/prettier/issues/5476 https://github.com/prettier/prettier/issues/3018 I know there is some reasoning why nested ternary indent was removed, but it's much harder to read code now. At least would be good to have option to remain nice formatting (from previous prettier version) - formatting of ternaries with indent and not under each other like: [code block] instead much easier to understand and read is: [code block]
requires to access `.default` after build while it's not required in dev (CJS dependency)
Describe the bug Encountered “Minified React error” in the production environment, the dev environment is fine. [code block] Reproduction Repo: https://github.com/songquanpeng/snippet-manager/tree/aa02a582c676bd3dcd5254f18d7087bb8a1a7220 My React application is on the `web` folder. System Info - `vite` version: 2.0.0 - Operating System: Windows 10 - Node version: v14.15.3 - Package manager (npm/yarn/pnpm) and version: 7.5.4 Summarization of the root problem https://github.com/vitejs/vite/issues/2139#issuecomment-1024852072
Verify CSS import ordering
A user on twitter reported that Next.js may not order CSS imports from JS correctly. We need to investigate and fix this! https://twitter.com/samselikoff/status/1299032241100787712 <sub>NEXT-1350</sub>
[NEXT-1187] Link navigation with loading.tsx is not instant for dynamic pages
Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.1.0: Sun Oct 9 20:14:30 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103 Binaries: Node: 18.12.1 npm: 8.19.2 Yarn: 1.22.19 pnpm: N/A Relevant packages: next: 13.0.6-canary.2 eslint-config-next: 13.0.5 react: 18.2.0 react-dom: 18.2.0 Which area of Next.js is affected? (leave empty if unsure) App directory (appDir: true), Routing (next/router, next/navigation, next/link) Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster https://github.com/tonypizzicato/next-13-loading To Reproduce - pull the repo - run `yarn install && yarn dev` - open `localhost:3000` in the browser - go to the "Careers" page - reload the page - set some throttling in devtools - click different pages in the menu - notice that "Careers" page loading state and route change are done instantly but with some delay for other pages Describe the Bug When you have a dynamic page with `loading.tsx` the route change and showing the loading animation are instant only for the page, which was freshly loaded. For other dynamic pages it hits the server first, then shows the loading state <img width="193" alt="Screenshot 2022-11-29 at 23 19 38" src="https://user-images.