All Issues
24,993 verified issues
[BUG] Platform-specific optional dependencies not being included in `package-lock.json` when reinstalling with `node_modules` present
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 [code block] I'm working on a team that utilizes a mix of x64-based and m1-based macs, and has CI build processes that uses musl. We're seeing that `npm` is skipping platform-specific optional dependencies for packages such as `@swc/core` as a result of the `package-lock.json` file being generated without all of them included. In our case, this then causes linting to throw an exception, because one of our eslint plugins depends on @swc, which depends on having the platform specific @swc package also installed. There seems to be at least two stages of cause to this. Firstly, when installing `@swc/core` from a clean slate working directory `npm` generates a `package-lock.json` with all of the optional dependencies for `@swc/core` listed: [code block] And it only installs the platform specific package: [code block] If I then remove my `package-lock.json`, leave my `node_modules` directory as-is, and then reinstall, I get: [code block] That is, it then generates a package-lock.json with only the platform-specific dependency that was installed on this machine, and not with the other optional dependencies that should also be listed. If you delete both `node_modules` AND `package-lock.json`, and then re-run `npm install`, it generates the correct lockfile with all of those optional dependencies list
Subscriptions/real-time API support
Unfortunately at the current point of time Prisma 2 doesn't yet support subscriptions (real-time API features). Prisma 1 followed a different architecture which provided support for subscriptions. We might be planning to bring back real-time/subscriptions functionality in the future based on a standalone "events engine" (which will use CDC under the hood). This issue tracks the progress for this feature. Please feel free to share your specific requirements and wishes for this feature. š
Property 'Authorization' does not exists on type 'AxiosHeaders' after upgrade to 1.2.2
Summary I'm getting the following error after upgrading axios to version 1.2.2: > TS2339: Property 'Authorization' does not exist on type 'AxiosHeaders | Partial<RawAxiosHeaders & MethodsHeaders & CommonHeaders>'. > Property 'Authorization' does not exist on type 'AxiosHeaders' The same snippet of code is working on version 1.2.1: [code block] Environment - Axios 1.2.2 - Node.js 18.12.1 - OS: Ubuntu 20.04.4 LTS (WSL2)
xcode 11.4 build fatal error: module map file xxx/Build/Products/Debug-iphoneos/YogaKit/YogaKit.modulemap' not found
Please provide all the information requested. Issues that do not follow this format are likely to stall. Description fatal error: module map file '/Users/miaohao/Library/Developer/Xcode/DerivedData/apex_baojia2-cdczyhhwbgshmtbdymitajpzamao/Build/Products/Debug-iphoneos/YogaKit/YogaKit.modulemap' not found React Native version: Run `react-native info` in your terminal and copy the results here. System: OS: macOS 10.15.3 CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz Memory: 219.52 MB / 8.00 GB Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.16.1 - /usr/local/bin/node Yarn: 1.22.0 - /usr/local/bin/yarn npm: 6.13.4 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.8.4 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2 Android SDK: API Levels: 23, 24, 25, 26, 27, 28, 29 Build Tools: 26.0.2, 28.0.3 System Images: android-23 | Android TV Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom Android NDK: Not Found IDEs: Android Studio: 3.6 AI-192.7142.36.36.6241897 Xcode: 11.4/11E146 - /usr/bin/xcodebuild Languages: Python: 2.7.16 - /usr/local/bin/python npmPackages: @react-native-community/cli: Not Found react: 16.11.0 => 16.11.0 react-native: 0.62.0 => 0.62.0 npmGlobalPackages: react-na
Add --no-overwrite option to aws s3 cp/mv
It would be nice to have a convenience function `--no-overwrite` for `aws s3 cp/mv` commands, which would check the target destination doesn't already exist before putting a file into an s3 bucket. Of course this logic couldn't be guaranteed by the AWS API (afaik...) and is vulnerable to race conditions, etc. But it would be helpful to prevent unintentional mistakes!
Lint multiple files in parallel [$500]
This is a discussion issue for adding ability to run eslint in parallel for multiple files. The idea is that ESLint is mostly CPU bound, not IO bound, so creating multiple threads (for machine with multiple cores) might (and probably will) increase performance in a meaningful way. The downside is that currently ESLint's codebase is synchronous. So this would require rewriting everything up to and including eslint.js to be asynchronous, which would be a major effort. I played with this a little while ago and found a few libraries for Node that handle thread pool, including detection of number of cores available on the machine. - Node-threads-a-gogo - seems pretty good, but looks dead. - nPool - seems actively in development, but has native components (C++) - Node WebWorkers - seems pretty dead too. - Parallel - seems dead, and no pool implementation. - Node Clusters - not stable yet, and probably isn't going to be available on Node v0.10 - WebWorkers - seems that they are only implemented in io.js And there are a ton of other libraries out there for this. If anyone had any experience writing multithreaded applications for node.js and would like to suggest alternatives or comment on the above list, please feel free. P.S. https://www.airpair.com/javascript/posts/which-async-javascript-libraries-should-i-use <bountysource-plugin> Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Make previous value available in @AfterUpdate function
By popular request, it would be very useful if we could also access the previous state of objects being updated in @AfterUpdate functions For example: [code block] Could become [code block] TypeORM already knows the previous value, as it will only call `@AfterUpdate` if it detects a change, therefore, the feature would only require that to be exposed to developer. Please see comment and thread - https://github.com/typeorm/typeorm/issues/1609#issuecomment-484303500 Thank you!
Use `JOIN`s in more queries
Problem Currently, there is no way to join tables together. Queries that include relations only include the relational data by using separate queries. Suggested solution I am hoping this can be implemented without a breaking API change. I would like to see a single query executed that joins multiple tables when necessary rather than a set of queries, each referencing a related table. Alternatives The only alternative I can see is to use raw queries.
Support for zod 4
Confirm this is a Node library issue and not an underlying OpenAI API issue - [x] This is an issue with the Node library Describe the bug Hey OpenAI team š After updating to Zod v4 Iām hitting this runtime error: [code block] Looks like the vendored `zod-to-json-schema` in `openai/helpers/zod` still expects the `ZodFirstPartyTypeKind` export, which was removed in Zod v4. Notes / ideas Pinning zod@3 is a temporary workaround, but it blocks upgrading the whole stack. A quick fix might be bumping the vendored zod-to-json-schema to a version that supports Zod v4 or swapping it out for the maintained `@asteasolutions/zod-to-openapi` which already handles the new internals. Thanks for taking a look! Let me know if I can help with more info or a PR. To Reproduce 1. Fresh project with pnpm 1. pnpm add openai@5.8.3 zod@^4 1. Add a simple script: `import { zodResponseFormat } from 'openai/helpers/zod'` 1. pnpm tsx index.ts (or just bundle with esbuild) ā error above. Code snippets [code block] OS macOS Node version Node v22 Library version Latest
0.4.0 release TODOs
I'm going to keep writing here features and changes I'm planning to introduce in 0.4.0: - [x] (breaking) instead of named connections as they are right now, make it possible to write connections, managers and repositories into exported variables, e.g. `const connection1 = createConnection(); const connection2 = createConnection();`, `const manager1 = connection1.manager; const manager2 = connection2.manager;`, etc. - [ ] (breaking) we need to change some names in the project to make things more clear. `Connection` should be renamed to `Storage` and `QueryBuilder` should be renamed to `Connection`. - [x] (breaking) remove transaction decorator ? - [x] (breaking) remove custom repository functionality? - [ ] (breaking) deprecate eager and lazy loading? - [x] (breaking) re-work current configuration loading and ormconfig file concept - [ ] re-work entity schemas and make them "primary way of defining a database schema model" - [ ] re-work QueryBuilder concept - [ ] make subset of changes regarding to how joins are used right now to implement entity streaming - [ ] provide a tutorial on how it can be easy to integrate typeorm and graphql - [ ] check if typeorm can be used with knex and provide a tutorial if possible - [ ] transpile it to es6 and support only node 10 to improve performance and make it easier to debug typeorm-based apps - [ ] add flag in find options to log query per-find-call - [ ] remove some magic methods from QueryBuilder (like joinAndMap) - [ ] add `saveAndRe
š Tracking: ESLint v9 support
š Hi all! With ESLint v9 released, many community plugins are adding support for the new major version. This is a tracking issue of ESLint v9 compatibility for the ~35 or so most popular plugins for ESLint that already support flat config. We'll keep this list updated over time. > If the plugin you're looking for isn't in this list, check š Tracking: Flat Config support. This list treats flat config support as a prerequisite for full ESLint 9 support. š Status emoji key: <ul> <li>ā Support released!</li> <li>š¦ Merged; pending release</li> <li>šļø PR was at least started</li> <li>š Issue filed; waiting for PR</li> </ul> <table> <thead> <th>Name</th> <th>Status</th> <th>Issue</th> <th>Commit / PR</th> <th>Version</th> </thead> <tbody> <tr> <th colspan="5">Plugins</th> </tr> <tr> <td> <a href="https://github.com/nuxt/eslint"> <code>@nuxt/eslint</code> </a> </td> <td>ā </td> <td></td> <td></td> <td>*</td> </tr> <tr> <td> <a href="https://github.com/typescript-eslint/typescript-eslint"> <code>@typescript-eslint</code> </a> </td> <td>ā </td> <td> <a href="https://github.com/typescript-eslint/typescript-eslint/issues/8
Conditional uniqueness constraints; Partial/Filtered (Unique) Indexes
Problem I would like to be able to define a uniqueness constraint that has conditional elements to it so that it can map to and align with a conditional unique index/constraint within the database. Suggested solution Modify the `@@unique` modifier to include a `where: { }` argument that could define the condition that allows this to be unique.
[FEATURE]: Support Polymorphic Association
Describe what you want I'm looking for a Typesafe ORM that support for polymorphic associations. To give a concrete example: I have a `Comment` model. I need this model to be associated with both `Article` and `Photo` models. Instead of creating separate tables or associations for comments on articles and comments on photos, I would prefer a unified approach where a single `Comment` can belong to either an `Article` or a `Photo`. Most ORMs (and query builders) except Prisma support polymorphic association. Prisma is not taking interest in solving this issue: https://github.com/prisma/prisma/issues/1644. If you plan on implementing Prisma, that would be a killer feature that would be a reason in itself to use Drizzle. A few teams have mentioned it explicitly in that issue. Do you plan to support and document this feature in the near future ?
Conditional operator or function for expression syntax
Describe the enhancement I'd like some kind of conditional operation added to expression syntax. This can be an actual ternary operator (`?` `:`) or a built-in function (e.g., `if(<condition>, <true-value>, <false-value>)`). Additional information There is a workaround: using shell scripts to evaluate the condition, setting step outputs, and having other steps reference those outputs. But it would be much cleaner to have some kind of ternary / if/then/else / conditional branching built in to the expression syntax.
Support for AWS Secrets Manager or Azure KeyVault in `schema.prisma`
Problem I'm using Prisma only to manage my database schema, not for the CRUD operations in code. The problem is that the schema.prisma file only supports defining the datasource URL using values defined in a file (dotenv). Since I don't want to store the database credentials in my project I'd like to obtain them from AWS Secrets Manager service. Suggested solution Provide a mechanism like a callback function to defined the datasource URL.
Feature Request: Support for private marketplace/gallery
We have created several VSIX extension that have no use to anybody else except our company. We would like to host our own private extension gallery and have an ability to specify alternative extension gallery paths (like "Additional Extension Galleries" in Visual Studio 2015). - VSCode Version: 1.10.1 - OS Version: Windows 10
Crash when rebuilding application menu on wayland
Extracted from https://github.com/microsoft/vscode/issues/181533#issuecomment-1565576439 [code block] @Mithras can you provide the following details to help us repro the issue, 1) Are you using custom or native titlebar ? 2) Are you starting the application with `--ozone-platform=wayland --enable-features=WaylandWindowDecorations` ? 3) Where did you install insiders from ? Snap, deb or rpm ? 4) A video recording showing the exact repro steps will be helpful.
browser: Can't resolve 'react-native-sqlite-storage'
Issue type: [ ] question [x] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [ ] `postgres` [ ] `sqlite` [x] `sqljs` [x] `react-native` TypeORM version: [x] `latest` [ ] `@next` [ ] `0.x.x` (or put your version here) Steps to reproduce or a small repository showing the problem: I followed the steps to use typeorm in the browser, including making the webpack changes. I end up with: [code block]
Support ES6 modules export / ESM
It would be great if the Prisma Client JS generator would be compatible with ES6 modules out of the box. Note: Related to prisma/prisma-client-js#175
typeorm findOneBy( { id: null or undefined } ) method return the first record on the table !
Expected Behavior Return `null` Actual Behavior Retrieve the first record from users table ! Example : [code block] Steps to Reproduce 1. Create typeorm connection 2. Create user entity and migrate it to the database 3. Query the database using the user repository then call `findOneBy` method . Relevant Database Driver(s) | DB Type | Reproducible | |-------------------| --- | | `sqlite` | yes | For other database drivers , i have no idea :)