All Issues
24,993 verified issues
[BUG] npm error TAR_BAD_ARCHIVE: Unrecognized archive format
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 ever I trying to install pm2 (some other packages also having this issue) globally using npm i -g pm2 it is showing me this error [code block] I tried this with yarn, pnpm also. Same issues facing using yarn or pnpm. I tried this with Ubuntu 22.04, Ubuntu 24.04, Fedora Cloud 41 Besides I also tried this with node-lts 18, 20, 22 and with latest npm. Expected Behavior _No response_ Steps To Reproduce 1. In this environment... 2. With this config... 3. Run '...' 4. See error... Environment - npm: 10.9.0, 11.0.0 - Node.js: LTS 18, 20 & 22 - OS Name: Ubuntu 22.04, Ubuntu 24.04, Fedora Cloud 41 - System Model Name: VPS - npm config: [code block]
Handle cast error on find when objectId is invalid
Do you want to request a feature or report a bug? Bug What is the current behavior? I'm trying to find an item by its _id, but when I try to handle the possible "error", when the client sends an id that doesn't exist and then return it as an user friendly error, it's getting into the "catch" function and resulting in an Error 500 to the user with a very big error message. I tried to find a method to handle it on google and even here, but I didn't find anything. If the current behavior is a bug, please provide the steps to reproduce. [code block] What is the expected behavior? I want to handle this kind of "error" that for me isn't an error. It's just an invalid item to search. Please mention your node.js, mongoose and MongoDB version.* Node: v7.4.0 Mongoose: 4.10.5 MongoDB: v3.4.4
Memory leak on high frequency data.
Hi All I am using oiredis to save some data in bulk, around 12k rows every second. the main issue that it happening is that node is not able to recover memory from the ioredis operation growing forever. I am saving the data in two stages, first one I received several thousand messages that are stored in memory reaching upto 140 mb then once a second I grab part of that data and I pipeline it into redis where grows to 1gb within 4 hours until it crash the process due the memory limitations. The easy fix it is to use "old --max-old-space-size" trick but everyone know that this does not fix the problem but the symptoms. Node version 12.4.0 NPM 6.9.0 ioredis 4.9.0 Windows 10 Any idea or recommendation, what is better ? reuse/create new connection, use/avoid await/async ? AA
React Native 0.79.1 errors
Describe the bug We are getting cannot find crypto and url when compiling with axios@1.9.0. [code block] To Reproduce _No response_ Code snippet [code block] Expected behavior _No response_ Axios Version _No response_ Adapter Version _No response_ Browser _No response_ Browser Version _No response_ Node.js Version _No response_ OS _No response_ Additional Library Versions [code block] Additional context/Screenshots [code block]
Support node22 in runs.using for JavaScript actions
Describe the bug Specifying `node22` as the runtime for JavaScript actions results in `System.ArgumentOutOfRangeException` error. Node.js v22 transitioned into LTS On October 29, 2024 To Reproduce [code block] Expected behavior - No errors. - Documentation is updated. Runner Version and Platform - Current runner version: 2.321.0 - Operating System: Ubuntu 24.04.1 LTS What's not working? [code block]
[BUG]: Deeply nested queries fail due to table name length
What version of `drizzle-orm` are you using? 0.30.1 What version of `drizzle-kit` are you using? 0.20.14 Describe the Bug When creating a query with deeply nested data, the sql generated uses names based on the relation names that have been set up, with more text being appended to the name for each level of depth. "table1" "table1_table2" "table1_table2_table3" etc... If this reaches the limit for the length of a table name, the database will truncate the names to the number of allowed characters, and fail with the error `error: table name "documentVersions_workflowStep_workflow_contract_entities_userEn" specified more than once` because there were multiple more tables in the name that are cut off. They instead all get truncated to the same string which causes an error. Expected behavior Drizzle should either use shorter names upon reaching the limit for a table name, or use aliases within the request that get turned back into the correct names upon response. This ideally should not be something the drizzle user has to worry about, as the query builder should preferably work without having to manually set table names for all the joins. Environment & setup This occurs using postgresql
exports lib packages in package.json
TLDRοΌ > Oh, yeah I don't think we will ever export that. https://github.com/axios/axios/issues/5000#issuecomment-1311350960 Is your feature request related to a problem? Please describe. Yes. I'm writing a adaptor to be used in userscript like tampermonkey or Violentmonkey, it use a xhr provided be broser extension `GM.xmlHttpRequest` to make cors request. And to make it behavior like axios' xhr adaptor, I'm using some axios' helper functions directly by [code block] But after axios 1.0.0 is released, a `exports` field is added to package.json, and lib directory is no longer exported anymore, this make me unable to use helper function provided by axios anymore. https://github.com/axios/axios/blob/484aa4fe6addccbd32206a31eb3d2d000843066e/package.json#L6-L17 modern js bundler will raise a error for this: `Package subpath './lib/core/buildFullPath' is not defined by "exports" in .../node_modules/axios/package.json` by bundler. Describe the solution you'd like add `lib` dir to `package.json#exports`
Refreshing the VS Code product icon
The Icon Journey...Version 2 _β οΈ NOTE: Please read our updated response based on the feedback β οΈ_ The 2017 icon change showed how much passion and interest there in the iconography for VS Code, and we thank you for that feedback. There are still a few outstanding issues with current icon, and weβve been spending time over the past few weeks looking at ways to resolve them. We wanted to share where we are and get your thoughts. The current icon is hard to see on some customers taskbars as well as in some parts of the Windows UI like the file chooser dialog. The size of the VS Code shape itself, when wrapped within the Visual Studio Family ribbon (the βwallβ on the right) makes the difference between Visual Studio and Visual Studio Code hard to spot, especially for some customers with color vision deficiency. Finally, some commented that the macOS version of the product icon looks out of place amongst other apps in the dock. An opportunity to learn As well as your feedback, there was also efforts going on inside Visual Studio and Visual Studio for Mac on aligning with iconography across Microsoft, being led by Windows and Office. Youβll have seen some of this in the latest product icons for Visual Studio (Windows) and Visual Studio for Mac as well as some of the recent Office icon updates. While this was not our main driver of change, it made sense to learn from the other work and leverage a similar style to solve some of the issues we were seeing. The proposed icons
Add support for `enum` string assignments
[code block]
Support APKs with 32-bit and 64-bit binaries within them
using `flutter build apk --release --flavor pro ` make apk file , but arm64-v8a do not include libflutter.so file.so app launch fail. when I add `--target-platform=android-arm64 `: `flutter build apk --release --flavor pro --target-platform=android-arm64`,apk file include so flie. But app launch fail on 32 bit cpu. what can i do, apk file can run on 64 and 32 cpu @mravn-google [code block] I create new project, debug or releas, work well. diffrece from new project from my project is that i add thrid party `so` file where is the problem ?
[Feature Request] Using stripe-node outside of Node.js (e.g. Cloudflare Workers or Deno)
I'm trying to setup a Stripe service as a serverless function using the Cloudflare Workers platform. But the `stripe-node` package seems to depend on Node.js APIs. Is it possible to use a subset of `stripe-node`'s functionalities for Cloudflare Workers? Is supporting Cloudlfare Workers something you are interested in? Using Stripe in a no-cold-start serverless environment would be quite lovely. Would it be possible to extract the business logic that is agnostic to Node.js and expose it to users? So that we can use all kinds of platforms beyond Node.js, such as the Deno or Cloudflare Workers. It could be a new package, e.g. `stripe-js`. Thanks for what you are doing at Stripe, it's such a lovely product. Related tickets: https://github.com/stripe/stripe-node/issues/871 https://github.com/stripe/stripe-node/issues/773.
alias '@' to path.resolve(__dirname, './src') is not working
Describe the bug Alias `{ '@': path.resolve(__dirname, './src') }` is not working. Reproduction project structure: [code block] vite.config.js: [code block] src/index.js [code block] Got error in vite: [code block] System Info - required `vite` version: 0.17.0 - required Operating System: Linux - required Node version: 14.3.0
Preview feature feedback: `jsonProtocol`
Our new Json Protocol is in early preview since 4.11.0. During performance investigations and optimizations, we noticed that the existing protocol implementation using GraphQL added a CPU and memory overhead that was especially noticeable for larger Prisma schemas. Therefore, we found an alternative way to express our queries without needing that overhead: JSON. To try out the new protocol, enable the `jsonProtocol` Preview feature in your Prisma schema: [code block] Regenerate Prisma Client to use the new JSON protocol. For environments or situations where it is not viable to enable the Preview feature flag to your Prisma schema file, we also added an environment variable that you can use to force the use of the JSON Protocol Preview feature: `PRISMA_ENGINE_PROTOCOL=json`. ~~Note: This is an early Preview feature with a significant limitation: Invalid input to Prisma Client will throw unpolished, internal errors that are less descriptive and user-friendly than our usual ones. We intend to improve these future releases.~~ ~~Using it with Data Proxy and Prisma Data Platform currently also leads to errors.~~ We expect using `jsonProtocol` to improve Prisma Client's startup performance and memory usage significantly. This will likely have a more significant impact on applications with larger Prisma schemas. We would appreciate your feedback on this feature on the following particularly: 1. Does using this preview feature introduce any regressions or problems in your app
Support for Read Replicas (Postgres, MySQL) or setting Client in read-only mode
Latest update Check this comment below for the Client Extension that enables this functionality! https://github.com/prisma/prisma/issues/172#issuecomment-1718089127 π₯³ --- @matthewmueller's update Problem Currently we don't support read-replicas. This is a common need for scaling databases. Solution I agree with @dpetrick's solution below. One thing I would additionally suggest is to provide a `Readonly` interface that you can pass through. This `Readonly` interface would omit the `Create`, `Update`, `Delete` methods. --- > Does prisma2 support the ability to direct queries to master db or read-only replicas based on read/write? This is useful functionality that lots of db drivers support. Hopefully since prisma2 aims to replace the db driver, it would also have this functionality. > > > (User feedback) > > This can be handled in various ways (the list if from the top of my mind): > > 1. Not natively in Prisma, have actual read/read-write nodes in the DB natively and multiple `datasource` blocks and multiple `generate` blocks to generate read-only, read-write photon. > > [code block] > > 2. Natively in Photon with a read only parameter > > [code block] > > Other ways are also possible. Additional context * https://github.com/prisma/prisma/issues/3389
React Native: Error: @firebase/firestore: ", "Firestore(4.10.1): Could not reach Firestore backend "
[REQUIRED] Describe your environment Operating System version: IOS (React Native), Android (React Native) Firebase SDK version: 4.12.0 Firebase Product: Firestore > Error: @firebase/firestore: ", "Firestore(4.10.1): Could not reach Firestore backend " Steps to reproduce: Add npm install firebase@4.12.0 --save to the react native project Add the code below to the project Nothing is happening (collections and documents were not created) Relevant Code: [code block] <img width="421" alt="screen shot 2018-04-05 at 15 50 21" src="https://user-images.githubusercontent.com/10096433/38366636-1bed5338-38e9-11e8-8018-f4274cd01fe3.png">
AWS DynamoDB Support
Would love to see support for DynamoDB in a future version π
[v2] Distribute binaries for alpine / musl libc
[code block] Errors with: [code block]
Please add an endpoint for getting account balance.
Please add an endpoint for getting account balance. e.g. `/balance` or `/account_details`. Many of us are creating products that use Anthropic's HTTP API where the user provides their API key. A good UX would be for the user to see their remaining balance. A user that is prepaying to their account will suffer a bad UX when their balance runs out. As an analogy, when my laptop battery is low, my machine doesn't suddenly power down while I am in the middle of a task. Instead I can observe the battery charge on my system tray, and a notification appears when it reaches 5%. This is a healthy UX. PS: It would be nice to have an `/account_details` endpoint that includes a list of timestamped API calls and their associated costs and IPs, as well as any other information that the user can retrieve from the web portal. However I can see this might be contentious when it comes to granting API keys for others to use. You'd have to tick checkboxes when creating an API key to grant individual functionalities. And that would be nice. If I could create an API key, uncheck "master-mode", set a per-day limit of $5, that would be nice. I could provide a capped API key to each user when I distribute my product. Or I could grant API keys to my team. And if I could create a "master-mode" API key for my own use, which lets me view my account details as well as details of any other API key I have generated, that would be nice. But this starts to become a medium-to-large sized task. Just p
βοΈ Lean Core
For the past several months we have been discussing and making progress on a project called βLean Coreβ. Please read our motivation for this project. Over the years React Native has accumulated a lot of parts that are now outdated, unused or otherwise legacy. It's time to clean everything up and put the repository into a much more manageable state going forward. This is an umbrella task intended to track all the work necessary to reach the goal of a leaner core, including work around repository reorganization. This issue is being kept up to date so new items will be added and completed ones will be (re)moved. Some of the items will spawn separate issues to track work. If you don't see a name assigned to any of the below items and you would like to help out, please volunteer in the comments and reach out to me to get started! Components & Runtime React Native currently comes with a large number of components, many of which are deprecated or outdated but they still part of the repository and increase the size of applications. For items in this section we are either looking to completely remove things if they are unused, or we'd like to move them either to community managed repositories or otherwise to facebookarchive. The list here is partially based on an awesome investigation by @axe-fb. The migration can be done roughly by following @matt-oakes's guide from further below: https://github.com/facebook/react-native/issues/23313#issuecomment-461462981 - [ ] Remove ImageSto
Why was the custom repository syntax changed?
I'm currently migrating from 0.2 to 0.3 and noticed that the syntax for custom repository was changed. I personally find this change very odd but I assume typeorm devs have a perfectly fine explanation for this - I lack to find it though. Remark: I know that this issue is not a documentation issue per se but SO is not the place to discuss things that's why I decided to post it here. Where I'm coming from: My project only uses a single relational database with various small custom repositories. Here is a simple example repository from 0.2: import {User} from "../bl/user"; import {EntityManager, EntityRepository, Repository} from "typeorm"; @EntityRepository(User) export class UserRepository extends Repository<User> { findByEmail(email: string): Promise<User | undefined> { // Implementation not relevant } isEmailAlreadyInUser(email: string): Promise<boolean> { // Implementation not relevant } } export function getUserRepository(manager: EntityManager): UserRepository { return manager.getCustomRepository(UserRepository); } New 0.3 version: // I have to manually create a type so UserRepository exists in type space. export type UserRepositoryType = Repository<User> & { findByEmail(email: string): Promise<User | null>; isEmailAlreadyInUser(email: string): Promise<boolean>; } // this UserRepository only exists in value space. Without my previous type