All Issues
24,993 verified issues
The inferred type of "X" cannot be named without a reference to "Y". This is likely not portable. A type annotation is necessary.
Bug Report 🔎 Search Terms inferred type cannot be named, symlink node_modules 🕗 Version & Regression Information I'm verifying the problem on the `typescript@4.1.3`. I've not tried older versions but at least is also reproducible on the `@next` version as of today. It is probably a regression or a corner case related with other issues opened and already closed like: - https://github.com/microsoft/TypeScript/issues/30858 - https://github.com/microsoft/TypeScript/issues/28689 - https://github.com/microsoft/TypeScript/issues/2338 - https://github.com/microsoft/TypeScript/issues/29221 ⏯ Playground Link Link for a repo where the problem is being reproduced > NOTE: Just clone the repo and run `yarn tsc` 💻 Code All the relevant code can be found at https://github.com/mistic/reproduce-typescript-problem-when-symlinking-node_modules It is just reproducing a similar setup that I had on other project that was generating the problem: - node_modules are a symlink to another location that is not a direct parent of the symlinked node_modules - we are using types in the compilation from a library where those types are just exported from other one, like for example `withRouter` within `react-router-dom` that is just a plain export from the same type on `react-router`. 🙁 Actual behavior I got the following error: [code block] 🙂 Expected behavior I was expecting no error at all and that the typescript compiler was just able to find all the respective modules. I've tried ev
Add Full-Text Search capability
This is a feature request for Full-Text Search functionality to perform a fulltext search on specific fields. Ideally with support for using GIN/GIST indexes to speed up full text search.
Vite dev hangs indefinitely without errors on page with many components and imports
Describe the bug I use SvelteKit. I have a somewhat complex page that contains quite a lot of components and imported functions. I had sporadic problems with this page hanging in the browser (both Firefox and Chrome). However, no error or notification in the vite cli. I was usually able to fix this by restarting the dev server several times whether or not in combination with restarting the browser. Other, simpler pages, always just kept working. Restarting my computer always works. In recent days, I have been adding extra functionality, and the more I added, the more often the page kept hanging and the harder I got it to work again. When I get the page online (after frequently restarting everything I get restarted), everything just works. Until I make an adjustment in the code and because of the HMR the thing hangs again. I don't see any other pattern to it. The problem does not occur when I build and preview the page, the production code always works. It's driving me crazy, I can hardly get anything developed. Reproduction I can't build a reproduction, there is no pattern. Steps to reproduce It happens only on the dev server. I can find no pattern, cannot pinpoint a cause and thus cannot foresee any reproduction. There is nothing wrong with the code itself, the production build works perfectly. The debug logs below are what I get when browsing to /leerlijn/54159. It starts doing it's thing, and then just randomly stops at some point. System Info [code block] Us
Tree shaking doesn't work with Typescript barrel files
Bug report I originally raised this as a discussion, but now I think it's a bug. Describe the bug When using a barrel file to re-export components from a single location, tree-shaking does not function correctly. To Reproduce I'm using Next 9.3.6 and I've arranged my components like: [code block] Each component file exports a single component, like this: [code block] index.ts is a barrel file that re-exports from each individual component file: [code block] I then use a couple of components in _app.tsx like: [code block] There's about 100 components defined, and only a couple are used in _app.tsx. But when I analyze the bundle I have a very large chunk, shared by all pages, and it contains all my components, resulting in an inflated app page size: <img width="748" alt="Screenshot 2020-05-06 09 35 32" src="https://user-images.githubusercontent.com/425787/81183292-f8bbdf00-8f7c-11ea-91c9-4b95adff907a.png"> I use a similar import strategy within pages, and every one of them appears to contain every component. my tsconfig.json is: [code block] and I'm using next's native support for the baseUrl field. I haven't changed the module or the target. When I change the _app.tsx imports to: [code block] the common bundle and app page size drops dramatically, as I would expect it to: <img width="751" alt="Screenshot 2020-05-06 09 34 21" src="https://user-images.githubusercontent.com/425787/81183384-1be68e80-8f7d-11ea-9aed-e32a1d871ab9.png"> Expected behavior The a
CSS module styling is removed too early on route changes
Bug report Describe the bug CSS module styling is removed immediately after clicking a `next/link`, instead of after the DOM is removed on production builds. This causes the components to have no styling at all during a page transition. This issue does not happen on dev mode. I believe this is a bug with CSS modules specifically because components styled with `styled-jsx` don't have this problem. Really would love to be able to use Sass via CSS modules here instead of re-writing the entire app I'm working on using `styled-jsx`. If Sass modules can't work in this scenario, I think I would be forced to use `styled-jsx`, which is not my preferred method of styling my components for this project. To Reproduce I have created repos, and deployed these repos to demonstrate the problem using framer-motion for page transitions. If you were to pull these repos and run them locally using `npm run dev`, you will see that the flash of unstyled content does not happen on any one of them in dev mode. However, on their deployed sites, you can see the flash of unstyled content with CSS modules and Sass modules. styled-jsx Behavior: correct, no flash of unstyled content Deployed site on Vercel Repo CSS modules Behavior: buggy, there is a flash of unstyled content immediately after clicking the link Deployed site on Vercel Repo Sass via CSS modules (additional) Behavior: buggy, there is a flash of unstyled content immediately after clicking the link (same as CSS modules) Deployed
Typed routes not working in Expo 51 and Expo router
Minimal reproducible example https://github.com/alfjesus/typed-routes What platform(s) does this occur on? _No response_ Did you reproduce this issue in a development build? No (tested in Expo Go) Summary Creating a new project with `yarn create expo-app` (Expo 51) seems to have broken the typed routes for expo router. When I downgraded to Expo 50 (and `npx expo install --check`), typed routes started to working again. I guess there's something wrong with the generation of the types when the development server starts 🤔 Environment expo-env-info 1.2.0 environment info: System: OS: macOS 14.4.1 Shell: 5.9 - /bin/zsh Binaries: Node: 18.19.0 - /usr/local/bin/node Yarn: 1.22.21 - /opt/homebrew/bin/yarn npm: 10.2.3 - /usr/local/bin/npm Watchman: 2024.01.22.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.13.0 - /Users/anders/.rbenv/shims/pod SDKs: iOS SDK: Platforms: DriverKit 23.4, iOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4 IDEs: Android Studio: 2023.2 AI-232.10300.40.2321.11567975 Xcode: 15.3/15E204a - /usr/bin/xcodebuild npmPackages: expo: ~51.0.0 => 51.0.0 expo-router: ~3.5.10 => 3.5.10 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.74.1 => 0.74.1 react-native-web: ~0.19.10 => 0.19.11 npmGlobalPackages: eas-cli: 7.8.2 Expo Workflow: managed Expo Doctor Diagnostics ✔ Check Expo
1.90 snap package crash on startup
Does this issue occur when all extensions are disabled?: Yes - VS Code Version: 1.90.0-insider 26c4a07b47a2bd34480a5e4cba2c2384c590b039 x64 - OS Version: Ubuntu 24.04 LTS Steps to Reproduce: 1. launch the code-insiders from terminal with command [code block]. it opens and then closes down. 2. here is the crash report(file_attached): crash_report.txt here is the snippet of crash logs that i feel is important: [code block] here "mypcname" is the placeholder for actual user login name. tried but didn't work: reference issue Workaround: running with `--use-gl=angle --use-angle=swiftshader`
May 2024 iOS privacy manifest requirements tracking issue
UPDATE We now have guide on how to add a privacy manifest via your app config (app.json / app.config.js). --- Overview Recently, Apple announced that, starting May 1, they would start enforcing that all new apps and updates must declare approved reasons for using specific APIs in a privacy manifest, preventing uploads to TestFlight if the requirement is not met. These requirements also apply to 3rd party SDK's, with specific SDK's identified by Apple requiring a signature in addition to the manifest. If you submitted to TestFlight after March 13th, you may have received an email from Apple with an "ITMS-91053" warning, indicating that they found API usage matching an `NSPrivacyAccessedAPI` category in your app that will require these changes in order to meet the requirements after May 1st (common categories might include `NSPrivacyAccessedAPICategoryDiskSpace` and `NSPrivacyAccessedAPICategoryFileTimestamp`). What Expo is doing about it Expo engineers are actively engaged with this issue, doing everything in our power ensure that your app submissions continue uninterrupted despite the relatively short notice: - Adding privacy manifests to all affected modules maintained by Expo - Tracking progress on key dependencies not maintained by Expo (e.g., this PR to add the manifest to `react-native`) and ensuring our version validation is updated accordingly as these updates go live. - Providing guidance on how to add the privacy manifest to community-maintained modules - Prov
Git: Preserve open files list when switching branches
I suggest for saving file opening status each git branches. I think the each branches need different files on the branches. If I changed branches and close and open files every time. Next time if I changed branch again, next process is closing opening files and opening files needed to edit. And next time...
Synchronized Scrolling in Split Editor
I have a feature request related to synchronized scrolling in the Split Editor. I checked for extensions and didn't see any. Was wondering if this is the pipeline or not.
[BUG] Npm opens many connections when installing
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 My project needs around 2000 packages. When running "npm install" it starts out by opening 2000 connections and then when all the connections are open it downloads 1 package on each connection. Is this intended?, because it causes a quite high load on our package proxy. Is there a way to limit the number of connections? With npm 9.9 it only uses 18/20 connections. Expected Behavior "npm install" only opens a few connetions to the package server. Steps To Reproduce 1. Clear cache 2. npm install or npm ci Environment - npm: 10.2.5 - Node.js: 18.19.0 - OS Name: Windows 11 - System Model Name: - npm config: [code block]
Configuration tries to use the registration endpoint even when passed `--token <token>`
Describe the bug When running the configuration of the runner unattended, some means of authenticating is required. The documentation at https://docs.github.com/en/rest/actions/self-hosted-runners#create-a-registration-token-for-an-organization claims that a token from that endpoint can be used with the `--token <token>` option. Instead, the runner attempts to obtain a new one with a PAT that may or may not be passed to it (See ConfigurationManager.cs#L111) In the case that it isn't, the configuration fails with a 404. To Reproduce Steps to reproduce the behavior: 1. Obtain a registration token from `https://api.github.com/orgs/ORG/actions/runners/registration-token`, where `ORG` is a valid organization. Call this registration token `TOKEN`. 2. Run `./config --unattended --url https://github.com/ORG --token TOKEN` 3. An error is printed out and the runner exits Expected behavior What is described to be possible in https://docs.github.com/en/rest/actions/self-hosted-runners#create-a-registration-token-for-an-organization Runner Version and Platform Version 2.291.1, Commit 496ec0df97891bd8e50f4431d01874ac3ab75a93 OS of the machine running the runner? OSX/Windows/Linux/... Linux, Ubuntu 20.04.4 LTS What's not working? [code block] Job Log Output N/A Runner and Worker's Diagnostic Logs N/A
Observatory port timeout on iOS
I'm unable to debug a freshly created app on physical iOS devices when pubspec dependencies reach a certain size, because it causes the "waiting for observatory port" step to timeout after 30 seconds. Devices tested: iPhone 8 iPhone 12 iPhone 12 Pro iOS versions tested: 14.2 14.2.1 14.3 Xcode versions tested: 12.2 12.3 Tests run using MacOS Catalina 10.15.7 on a late 2019 MBP 16". Simply commenting out random pubspec dependencies from the below, cleaning and rebuilding allows debugging to attach - sometimes just barely, at the 28 second or 29 second mark. Here's a triggering pubspec: [code block]
[FlatList] FlatList and VirtualizedList Scroll performance is laggy after 30+ rows .
Description Flatlist or VirtualizedList Scroll lags horribly after 30-40 rows . I am fetching the same data on onEndReached . Upto 30 rows its looks fine , but after that scrolling drops several frames . When I disable virtualization , scroll becomes normal but but responsiveness goes away . I tried disabling virtualizing on scrolling velocity this way . isVirtualizationTrue(e){ var dOffset=(e.nativeEvent.contentOffset.y- this.state.lastOffset) var dt=(e.timeStamp-this.state.lastTimeStamp) var velocity = dOffset/dt var isInstant=velocity-this.state.lastVelocity>.01 if(velocity<1 && !isInstant){ return false } if(velocity>1){ return true } if(velocity <.25){ return true } } But again , there's problem for the unmounted Component that are removed from the views , which takes long time to show up again . Is there any way to improve the scroll performance ? Here's my sample code <FlatList shouldItemUpdate={(props,nextProps)=> { return props.item!==nextProps.item } } onEndReached={this.onRefresh.bind(this)} onEndReachedThreshold={200} onRefresh={this.onRefresh.bind(this)} refreshing={this.props.Feed.isFetching } data={this.state.items} renderItem={this.renderItem.bind(this)} /> My data is sort
variable colors with <alpha-value> not working with theme function on plugins
I'm trying to create a plugin for Tailwind 3.1.8, but when I use variables on colors with the new syntax - `rgb(var(--primary) / <alpha-value>)` - the color stop working. I created an example on https://play.tailwindcss.com/2apCJBfHdC Removing the `/ <alpha-value>` from the color value make things work again. I'm doing something wrong?
Expose shell integration command knowledge to extensions
Shell integration in the terminal could enable APIs like being able to listen to commands that run and get their output/exit code. Rough example: [code block]
[BUG] npm install will randomly hang forever and cannot be closed when this occurs
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 When running `npm install` it will sometimes hang at a random point. When it does this, it is stuck forever. CTRL+C will do nothing the first time that combination is pressed when this has occurred. Pressing that key combination the second time will make the current line (the one showing the little progress bar) disappear but that's it. No further responses to that key combination are observed. The CMD (or Powershell) window cannot be closed regardless. The process cannot be killed by Task Manager either (Access Denied, although I'm an Administrator user so I'd assume the real reason is something non-permissions related). The only way I have found to close it is to reboot the machine. My suspicion is it's some sort of deadlock, but this is a guess and I have no idea how to further investigate this. I've tried using Process Explorer to check for handles to files in the project directory from other processes but there are none. There are handles held by the Node process npm is using, and one for the CMD window hosting it, but that's it. Even running with `log-level silly` yields no useful information. When it freezes there are no warnings or errors, it just sits on the line it was on. This is some log output from one of the times when it got stuck (I should again emphasise that the point whe
[NEXT-1308] Css is imported multiple times and out of order in /app dir
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/ssijak/next-css-issue-not-working-simple To Reproduce Just start the app and check the styling on the buttons. Styles are imported multiple times wherever `Button` was used (page and layout) and order is also not deterministic, so it can be imported in different order on different app runs. This is another/same simple repro difference is just that it uses turbo and transpiles the UI lib, I started with that but figured that the issue is happening without it too https://github.com/ssijak/next-css-issue-not-working Describe the Bug \-Same styles are imported multiple times \-Order of imports is not deterministic Screenshot: https://share.cleanshot.com/nq35j7vh Expected Behavior Same styles should be imported once. Starting the app multiple times should not produce different results (ordering of CSS, impacting specificity) Which browser are you using? (if relevant) No response How are you deploying your application? (if relevant) No response* <sub>From SyncLinear.com | NEXT-1308</sub>
next-lint Doesn't Support ESLint 9
Link to the code that reproduces this issue https://codesandbox.io/p/devbox/vigilant-pine-6wmz8y To Reproduce 1. Add `next lint` script to package.json per https://nextjs.org/docs/app/building-your-application/configuring/eslint 2. Add `.eslintrc.json` to project per https://nextjs.org/docs/app/building-your-application/configuring/eslint [code block] 3. Run lint and get an error [code block] Current vs. Expected behavior Expected lint to run successfully, but it failed with errors. Provide environment information [code block] Which area(s) are affected? (Select all that apply) ESLint (eslint-config-next) Which stage(s) are affected? (Select all that apply) next dev (local), next build (local), next start (local) Additional context It looks like this is coming from https://github.com/vercel/next.js/blob/canary/packages/next/src/cli/next-lint.ts. This needs to be changed to support ESLint 9's flat config https://eslint.org/docs/latest/use/migrate-to-9.0.0#flat-config. The migration guide is at https://eslint.org/docs/latest/use/configure/migration-guide <sub>NEXT-3112</sub>
AxiosError: maxContentLength size of -1 exceeded
Doing an axiosRequest with const a = await axios.get(URL) and without any further configuration, it gives error: ' AxiosError: maxContentLength size of -1 exceeded' The contentLength of the website is significant, >185KB, but as I did not configure any maxContentLength then this behaviour is nonsense. What's the fix? Tried configuring a huge maxContentLength but still shows the error