All Issues
24,993 verified issues
[BUG]: how to recover from snapshot.json data is malformed
What version of `drizzle-orm` are you using? latest What version of `drizzle-kit` are you using? latest Describe the Bug When trying `drizzle-kit generate:sqlite --config drizzle.config.ts` I get [code block] the json doesnt have any syntax errors Expected behavior migration created Environment & setup MAC OS 14.0 (23A339) node v20.9.0 the JSON: [code block]
[BUG]: drizzle-zod 0.8.1 createInsertSchema / zod.infer not returning correct type
Report hasn't been filed before. - [x] I have verified that the bug I'm about to report hasn't been filed before. What version of `drizzle-orm` are you using? 0.43.1 What version of `drizzle-kit` are you using? 0.31.1 Other packages drizzle-zod@0.8.1 zod@3.25.1 Describe the Bug Drizzle-Zod createInsertSchema() does not create a valid schema. Subsequet `z.infer<typeof Schema> ` throw an error. example [code block] error of first infer usage: [code block] error of second infer usage: [code block] tsconfig [code block] Thanks a lot for any help on this!
Latest release has typescript issues
Describe the bug After the new GPT-3.5 update, building my typescript app now failed. I get errors: [code block] To Reproduce npm i openai@latest npm run build Code snippets _No response_ OS windows/linux Node version 18 Library version 3.2.0
Running on root directory "Failed to resolve entry for package"
Describe the bug When running on Linux, in the root directory, if you try to access vite_url:3000/path-of-working-dir, you will get the following error: [code block] Steps to reproduce: 1. `cd /` 2. `npm create vite@latest my-vue-app -- --template vue` 3. `cd my-vue-app` 4. `npm run dev` 5. Access `http://192.168.64.13:3000/my-vue-app` 6. See error If `my-vue-app` is on any other folder other than `/` (root directory) this error doesn't happen. This is running on a Ubuntu VM inside my M1 Pro Macbook. Reproduction Reproduction steps above System Info [code block] Used Package Manager npm Logs [code block] ``` Validations - [X] Follow our Code of Conduct - [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] 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/core instead. - [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. - [X] The provided reproduction is a minimal reproducible example of the bug.
[BUG]: Drizzle Studio CORS error
What version of `drizzle-orm` are you using? 0.29.3 What version of `drizzle-kit` are you using? 0.20.13 Describe the Bug Unable to use drizzle-studio due to CORS error. 1. Visit https://local.drizzle.studio/ 2. Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:4983/. (Reason: CORS request did not succeed). Status code: (null). Expected behavior _No response_ Environment & setup _No response_
[BUG]: drizzle-kit generate not working without error
Report hasn't been filed before. - [x] I have verified that the bug I'm about to report hasn't been filed before. What version of `drizzle-orm` are you using? 1.0.0-beta.2-58a4521 What version of `drizzle-kit` are you using? 1.0.0-beta.2-58a4521 Other packages _No response_ Describe the Bug I updated from beta1 to beta2. After doing some schema changes I wanted to generate the migration files. This told me to run drizzle-kit up, which i did. [code block] Then i run generate again and it still told me to run the up command. The meta folder did not get deleted. Maybe a separate bug which was already mentioned on Discord. After deleting the meta folder manually i run generate again and then it fails without any information: [code block]
[BUG]: drizzle-kit introspect fails on required param that is defined
What version of `drizzle-orm` are you using? 0.32.1 What version of `drizzle-kit` are you using? 0.23.1 Describe the Bug `drizzle-kit introspect` stops introspection for required param, even though it is defined. Affected version `0.23.1` Working local version: `0.22.8` (did not test other versions) introspect output [code block] config; [code block] env: [code block] env is correct and tested, config works with `0.22.8` Expected behavior Introspect running normally on version `0.22.8`: [code block] Environment & setup OS: `Ubuntu 22.04.4 LTS (Jammy Jellyfish)` PostgreSQL: `16.3 on x86_64-pc-linux-gnu`
npm install fails: @radix-ui/react-badge package does not exist on registry
Running npm install throws E404 for @radix-ui/react-badge. This package does not exist on the npm registry — Radix UI does not publish a separate badge component. The same mistake happens with other non-existent @radix-ui/* packages like @radix-ui/react-command (use cmdk instead). AI-generated package.json files commonly include phantom Radix UI package names.
allow narrowing from any
There are numerous questions as to why `any` cannot be narrowed from. Despite being natural and intuitive this feature was rejected due to being a serious breaking change to poorly written yet massive code bases. Please consider putting it behind a flag provided the evident need for it. TLDR - `any` is not what you think it is (poor naming at play) - for narrowing use `type unknown = {} | undefined | null | void` instead - yes, it's a hot unfortunate mess - no, there is no painless way to fix it - yes, you gonna need to fix your `*.d.ts` by hands - why? to make average JS developers happy with their less than perfect code - welcome to the club! get your badge at the reception UPDATE @yortus made a branch per https://github.com/Microsoft/TypeScript/issues/9999#issuecomment-238070961 where narrowing from `any` works! try it: `npm install typescript-narrowany`
Error: cyclic dependency detected
Running the latest version of Node.js on macOS. Also running the latest version of Mongoose. Seeing `Error: cyclic dependency detected` with literally no way to debug. Everything points back to Mongoose. Any suggestions? Started happening today. [code block]
Not able to get the list of rooms the client is currently in on disconnect event
I am trying to find the list of rooms a client is currently in on disconnect event (closes the browsers / reloading the page / internet connection was dropped) and based on my question on SO it looks like it is not possible. I find it hard to believe that this is the case (I think this is frequently needed functionality). Can any socket.io guru tell whether this is true or even better how can I achieve this?
TypeError: Converting circular structure to JSON
Version: 3.8.1 Code Snippet [code block] Exception/Log [code block]
Retries per request limit
I'm migrating to ioredis from node_redis and cannot find max_attempts feature analog, is this about me bad in searching? It's limit for retries per each request after which it will just fail. I can implement it on my own as a wrapper but I need to stop requests so that they will not continue to try requesting and this feature is also missing.
why does socket.io uses websocket connection and xhr polling parallel?
Hi, I am new to socket.io and am wondering why socket.io keeps up two connections: 1. Websocket 2. XHR polling at the same time? Isn't this a bit stupid?
Missing/broken sourcemaps for JS modules w/ imports when used with Vue
Describe the bug I originally reported this to JetBrains, and they seem to think it's an issue caused by sourcemaps not being generated by Vite. The same project moved over, running, and debugging on Vue-CLI does not have this issue and breakpoints are hit in the correct file. https://youtrack.jetbrains.com/issue/WEB-55544 IntelliJ/WebStorm/VSCode seems to be unable to properly debug local JavaScript files when debugging JS modules imported into Vue components in a Vite project. If you import a regular JS module into your component which itself has an import IJ/WS/VSC is unable to properly map the local .js file to the remote file for JavaScript debugging purposes due to missing/broken sourcemaps. When you place a breakpoint in your JS module source a new, read-only copy of the remote file is loaded from http://localhost:3000/src/xxx/xxx.js in the IDE and the breakpoint stops there instead of in the original JS file. This means that you have to debug in a read-only copy and then swap to your local copy for edits, which can be a big pain. It looks like this only happens when the modules themselves have imports. You can see that the remote file has a changed "import" line and so that might be causing it to not match up. Here's a screenshot from a sample project where the import inside the module causes the mismatch. You can see this difference between the local and "remote" on line 1. I've also created an example project which replicates this issue. https://github.com/Sm
TypeORM and Next.js
I spent some days configuring typeorm (postgresql) for Next JS but i didn't succeed. Most tutorials explain how to use prisma with Next JS. here are the steps I have taken: I installed pg, reflect-metadata, @types/react, @types/node, typeorm I generated the typeorm files using npx typeorm init I edited the ormconfig.js How to create a typeorm connection and use it in next js ? any good tutorial about using typeorm in next.js ?
'SplashScreen.show' has already been called for given view controller.
Summary This warning comes up on initial launch. Also I somtimes still get the ' No native splash screen registered for given view controller. Call 'SplashScreen.show' for given view controller first' error even though i'm upgraded to the latest beta which was supposed to address this issue Managed or bare workflow? If you have made manual changes inside of the `ios/` or `android/` directories in your project, the answer is bare! managed What platform(s) does this occur on? iOS Environment Expo CLI 4.12.6 environment info: System: OS: macOS 11.6 Shell: 5.8 - /bin/zsh Binaries: Node: 14.15.1 - /usr/local/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 7.8.0 - /usr/local/bin/npm Watchman: 2021.10.04.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0 IDEs: Android Studio: 4.1 AI-201.8743.12.41.6858069 Xcode: 13.0/13A233 - /usr/bin/xcodebuild npmPackages: expo: ^43.0.0-beta.4 => 43.0.0-beta.4 react: 17.0.1 => 17.0.1 react-dom: 17.0.1 => 17.0.1 react-native: 0.64.2 => 0.64.2 react-native-web: 0.17.1 => 0.17.1 npmGlobalPackages: expo-cli: 4.12.6 Expo Workflow: managed Reproducible demo or steps to reproduce from a blank project https://github.com/haibert/SplashScreenIssue I created a blank project with a custom dev c
API Gateway and postgresql logging not working for local development
Bug report `API Gateway` and `postgresql` logging not working for local development. It is very frustrating that the supabase team is not working to improve the local development experience. I even updated the supabase. Deleted the complete docker images plus volumes and restarted the local environment. Still, it does not work. Also before that, I tried `supabase db reset` it also didn't work. Expected behavior One should not get a 502 error. Screenshots <img width="1440" alt="Screenshot 2024-05-27 at 5 08 14 AM" src="https://github.com/supabase/supabase/assets/21134455/4a6deeb9-45e5-4fc7-8e4a-65e290ec4369"> <img width="1440" alt="Screenshot 2024-05-27 at 5 08 28 AM" src="https://github.com/supabase/supabase/assets/21134455/4567c831-c5f8-4ef4-a036-204593dfc06b"> My config.toml file [code block]
drive API: file upload stream backpressure issue
It seems that upload stream backpressure is not handled properly. In the following example, the stream is consumed very quickly (100% reached in 2 seconds) whereas the upload take a while... (that is expected with my ADSL connexion). This mean that the whole file is loaded into memory then sent gradually, which disables the benefit of the streams. Using your example: [code block] Configuration: Node.js v10.10.0 googleapis 33.0.0 OS windows7
TypeError: getProcessedPlugins is not a function
Describe the problem: Upgraded from TailwindCSS 1.9.6 to 2.0.1 for my angular project following the instructions on their website. I had previously used the following guide: https://notiz.dev/blog/angular-10-with-tailwindcss#setup to Install the previous version and that worked before. Please see error below: [code block]