All Issues
24,993 verified issues
ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'.
Description Recentrly update React ANtive Version to `"react-native": "0.68.0",` and have this issue ` WARN ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'. WARN ColorPropType will be removed from React Native. Migrate to ColorPropType exported from 'deprecated-react-native-prop-types'. WARN ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'. WARN ColorPropType will be removed from React Native. Migrate to ColorPropType exported from 'deprecated-react-native-prop-types'. WARN ColorPropType will be removed from React Native. Migrate to ColorPropType exported from 'deprecated-react-native-prop-types'. WARN ColorPropType will be removed from React Native. Migrate to ColorPropType exported from 'deprecated-react-native-prop-types'. WARN ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'. WARN ColorPropType will be removed from React Native. Migrate to ColorPropType exported from 'deprecated-react-native-prop-types'. WARN ColorPropType will be removed from React Native. Migrate to ColorPropType exported from 'deprecated-react-native-prop-types'. WARN ViewPropTypes will be removed from React Native. Migrate to ViewPropTypes exported from 'deprecated-react-native-prop-types'. WARN ColorPropType will be removed from React Native. Migrate
Add way to exclude fields via query arguments or globally
Problem Sometimes it is helpful to just remove some fields from the selection set like `password` so that we accidentally don't expose them to the frontend. Proposals Adding a `exclude` key in the arguments of the queries to easily exclude fields from the selectionSet just like `include` or `select`. [code block] Or [code block] Alternatives 1. Use query and list all the fields you want 1. Schema annotation 2. Manual omission via lodash or something !? Related - https://github.com/prisma/prisma/issues/2170 - https://github.com/prisma/prisma/issues/3246
Filename encoding errors
Hello all I'm using `aws s3 sync` to upload to a bucket, but I'm getting errors on many files: [code block] My system is Ubuntu Server 14.04 running aws-cli 1.7.5 and Python 2.7.6. I've altered my installations locale to `en_US.UTF-8` using `export LC_ALL=en_US.UTF-8`, but that didn't change anything. The filesystem is ext4, and the files in question have been created by OSX via Netatalk 3.1.7 (AFP). Any suggestions very much welcome...
Set a code/status for "Network Error"
I'm trying to detect when my server is down so that I can display an appropriate error message to the user. In this case, axios network requests throw an error which is different from all other axios errors, as discussed here: https://github.com/mzabriskie/axios/issues/204 In my code, it seems the only way to detect this error is to check err.message: `if (err.message === "Network Error"){/tell user the server is down/}` This bothers me because string comparisons are a little risky; perhaps some day this message will be translated, and my code will fail. It would be great if err.status or err.code (or err.???) were set to some documented value that we can check for in our code. Is there any other way to detect this scenario that I'm missing? Thanks all!
Twilio client is of type of any when using Twilio import in typescript
Issue Summary When using Twilio v4 library the Twilio client is of type any. Steps to Reproduce [code block] the type of twilio_client is any in version 4 whereas in version 3 it used to be the correct type i.e. TwilioClient. Code Snippet [code block] Technical details: twilio-node version: v4 node version: v14.17.3
feat: overwrite query key on trpc.useQuery options
Describe the feature you'd like to request I have query procedure `listPosts` which accepts some generic `parameters` and and optional `lastUpdatedAt` timestamp. The query key looks something like this: [code block] This query is expensive, so I cache it also on the server with the given `parameters` as caching key in case multiple clients request the same data. When I receive the same `parameters` on the server, I return the data from the cache. Now I need some way for clients to force a refresh on the server returning new data instead of cached data for the same `parameters`. So in this case, I query the `listPosts` with an optional `lastUpdatedAt` timestamp. The query key is now: [code block] The servers receives the same `parameters` as before and finds the data in the cache, but the `lastUpdatedAt` timestamp is greater than the cached timestamp. So it runs the expensive operation on the server and returns the new data (and caches it). Now I have two query keys on the client which are logically the same. I must update the query data of key 1 and key 2 with new data, because query key 2 is only temporary to trigger a server cache-invalidation. The `lastUpdatedAt` that I sent in query key 2 is a local state that will get lost after page navigation. When I later get back to the `ListPosts` page, it will use query key 1 again with data which was maybe set by query key 2. I'm currently using `onSuccess` of `useQuery` to set the query data of all query keys matching t
[BUG] Can't install `camelcase`, `decamelize` and other camel-related packages (#camelgate)
> STATUS: > ✅ Cloudflare marked it as resolved: > This issue is now resolved. - 19:42 UTC > ✅ NPM marked it as resolved: > This incident has been resolved. - 19:40 UTC > 👀 NPM is monitoring the situation: > A fix has been implemented and we are monitoring the results. - 17:37 UTC > 👀 Cloudflare disabled the rule and is monitoring the situation: > We have disabled the rule in question, and the rate of false positives is decreasing. We are monitoring. - 17:31 UTC > ✅ Seems to be working again - 17:13:17 UTC GET BACK TO WORK, NERDS! > ✅ NPM fixed: > The issue has been identified and a fix is being implemented. - 17:11 UTC > 🛠️ Cloudflare is fixing: > Identified - Cloudflare has identified an issue with the managed ruleset "Apache Camel - Remote Code Execution - CVE:CVE-2025-29891" which is potentially causing false positives. Customers can disable this rule by setting Action -> Log in the Cloudflare Dashboard. Other WAF rules are unaffected. We are currently working on a fix for this issue. > 👀 NPM is investigating: > We are currently investigating reports of intermittent failures when viewing and installing packages scoped to certain keywords. - 16:40 UTC > 👀 First failure in our CI - 15:49:08 UTC Caused by https://developers.cloudflare.com/waf/change-log/2025-03-11-emergency/ 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 Affected packages registry.
Server-Side-Request Forgery vulnerability introduced in npm 10.4 [BUG] <title>
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 Expected Behavior no SNYK detected security vulnerabilities Steps To Reproduce 1. In this environment... 2. With this config... 3. Run '...' 4. See error... Nothing to reproduce, this is a security vulnerability. Environment - npm: 10.4 - Node.js: 20.9.0 - OS Name: Windows 10 - System Model Name: Dell Evo - npm config: [code block]
Make edge compatible version
Right now there is a reliance on `fs` and other native node modules which do not exist in the Vercel edge runtime. It would be amazing if we could publish a `langchain/edge` with the functionality that can be run at edge
Server-Side Request Forgery Vulnerability (CVE-2024-39338)
Describe the bug Axios is vulnerable to a Server-Side Request Forgery attack caused by unexpected behaviour where requests for path relative URLS gets processed as protocol relative URLs. This could be leveraged by an attacker to perform arbitrary requests from the server, potentially accessing internal systems or exfiltrating sensitive data. To Reproduce In this vulnerable code snippet, the developer intended to invoke a path relative to the base URL, however it allows an attacker to craft a malicious protocol-relative URL which is then requested by the server. Given protocol-relative URLs are not relevant server-side as there is no protocol to be relative to, the expected result would be an error. Instead, a valid URL is produced and requested. Example Vulnerable Code [code block] Expected Output (Prior to axios 1.3.2): [code block] Developer might also have expected: [code block] Observed Output: [code block] This behaviour is potentially unexpected and introduces the potential for attackers to request URLs on arbitrary hosts other than the host in the base URL. The code related to parsing and preparing the URL for server-side requests, prior to version 1.3.2, only passed one argument to the Node.js URL class. [code block] Version 1.3.2 introduced `http://localhost` as a base URL for relative paths (https://github.com/axios/axios/issues/5458) [code block] As protocol-relative URLs are considered to be absolute, the config.baseURL value is ignored so protocol-re
File Nesting
Is there any possible chance we might see File Nesting in Visual Studio Code the same way it works in Visual Studio 2015? It was really convenient and helpful. I would adore such a feature!
[Whisper] cannot call `createTranscription` function from Node.js due to File API
Describe the bug Cannot call `createTranscription` function like below: [code block] This is because `createTranscription` interface asks me for File API, which is mainly for Browser API. [code block] How can I use this function from Node.js? Thanks! --- [code block] To Reproduce [code block] Code snippets _No response_ OS MacOS Node version Node v18.14.2 Library version openai v3.2.1
📈 Tracking: Flat Config support
👋 Hi all! With flat config stabilized and ESLint v9 ~on the horizon~ _released!_, many community plugins are adding native support for flat config. The Configuration Migration Guide provides docs on how to do that. This is a tracking issue of the <strike>~50</strike> ~70 or so most popular community integrations and plugins for ESLint. We'll keep this list updated over time. > See also 📈 Tracking: ESLint v9 support for plugins additionally supporting ESLint v9. 📌 Status and Types emoji key: <ul> <li>✅ Full support released!</li> <li>🌗 Partial support released</li> <li>📦 Merged; pending release</li> <li>🏗️ PR was at least started</li> <li>📝 Issue filed; waiting for PR</li> <li>❌ Not supported; no issue filed</li> <li>❓ Unknown</li> <li>🛑 Known blocker</li> </ul> <table> <thead> <th>Name</th> <th>Status</th> <th>Types</th> <th>Issue</th> <th>Commit / PR</th> <th>Version</th> <th>Blocker</th> </thead> <tbody> <tr> <th colspan="7">Editor Extensions</th> </tr> <tr> <td> <a href="https://github.com/SublimeLinter/SublimeLinter-eslint"> Sublime Text </a> </td> <td>✅</td> <td><em>n/a</em></td> </tr> <tr> <td> <a href="https://github.com/Microsoft/vscode-eslint"> VS Code
aws ecr get-login broken in latest rc build
$ `aws ecr get-login` unknown shorthand flag: 'e' in -e See 'docker login --help'. $ docker --version Docker version 17.06.0-ce-rc4, build 29fcd5d
Skip resources if already exist
This is a (Feature Proposal) Description For bug reports: What went wrong? I had a bug that cloudformation just stuck at UPDATE_ROLLBACK_FAILED. So I should to delete the stack and deploy serverless again. But now I got another problem: [code block] What did you expect should have happened? I think that database is too critical in production level to wont use Retain, In a simple wrong deploy or remove the stack can banish all your tables, wrong deploy can easily rollback but data is really critical. So I suggest to have something like: `serverless deploy --skipResources`, so it wlll skip the resources that already exist and cloudformation wont bring that error. Similar or dependent issues: #3148 Additional Data Serverless Framework Version you're using: 1.6.1 Operating System: Mac OS El Capitan Stack Trace: Provider Error messages*:
[Request for feedback] Nullable types, `null` and `undefined`
With the work on Nullable types in https://github.com/Microsoft/TypeScript/pull/7140, we would like to field some user input on the current design proposal. First some background: `null` and `undefined` JavaScript has two ways that developers use today to denote `uninitialized` or `no-value`. the two behave differently. where as null is completely left to user choice, there is no way of opting out of `undefined` , so: [code block] `a` will always implicitly has `undefined`, and so will the return type of `bar`. Nullability Given the JS semantics outlined above, what does a nullable type `T?` mean: 1. `T | null | undefined` 2. `T | undefined` 1. `T | null | undefined` It is rather subtle what `?` means in different contexts: [code block] 2. `T | undefined` This is more consistent, the `?` always means to `| undefined`; no confusion here. `T??` can be used to mean `T | undefined | null` or `T? | null`
docker-compose pull fails with error image not found for private repos
I have just set up a new cloud server with Ubuntu 14.04.2, Docker 1.7.0 and Docker Compose 1.2.0. When I am executing, docker-compose up -d, I am getting the following errors (the image is coming from a private repo) Traceback (most recent call last): File "<string>", line 3, in <module> File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.main", line 31, in main File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command", line 21, in sys_dispatch File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.command", line 27, in dispatch File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command", line 24, in dispatch File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.command", line 59, in perform_command File "/code/build/docker-compose/out00-PYZ.pyz/compose.cli.main", line 464, in up File "/code/build/docker-compose/out00-PYZ.pyz/compose.project", line 208, in up File "/code/build/docker-compose/out00-PYZ.pyz/compose.service", line 214, in recreate_containers File "/code/build/docker-compose/out00-PYZ.pyz/compose.service", line 199, in create_container File "/code/build/docker-compose/out00-PYZ.pyz/compose.progress_stream", line 37, in stream_output File "/code/build/docker-compose/out00-PYZ.pyz/compose.progress_stream", line 50, in print_output_event compose.progress_stream.StreamOutputError: Error: image togger/main-db:2.1.2 not found any help would be greatly appreciated
In Firefox, connection .... was interrupted while the page was loading
Hi, it shows connection to ws:..... was interrupted while the page was loading in Firefox but works. I saw many possible fix suggestions on different sites but none of them work now. It works fine in other browsers without any error/warning in the console. I am using socket.io 1.3.4 and firefox latest version 35.0.1.
React Native support
Is or will React Native be supported?
Enable Go to Implementation in Typescript Editors
Could you provide a way for Typescript Editors to list the implementations of a type? This would definitely help developer productivity to be able to find implementations of types faster. For example, in the Atom Editor atom-typescript plugin you can press F12 to 'Go to Declaration' which as currently implemented you often arrive at the typescript .d.ts file which has the function signature but not the actual implementation. Since the Typescript parser often generates the d.ts files from the .ts implementation files. Could that association between the d.ts and .ts files be preserved (perhaps output with a typescript compiler option) so that Typescript editors could take developers to a list of the implementing classes or functions? I opened a similar request for the Atom-typescript editor, but they indicate that they cannot implement this without Typescript parser support: TypeStrong/atom-typescript#790