All Issues
24,993 verified issues
tailwindcss in watch mode doesn't refresh outupt when files are changed using vim
This is based on #7679 - the versions being used are listed there. I ended up setting up test-case project here: https://github.com/javornikolov/tailwindcss-issue-7679 There is Github Actions CI job which outlines the changes I do to reproduce the issue. However the issue does't occur when running the automated scripts. It occurs when I manually edit the file using `vim` editor (doing the same changes). `vim` version is 8.2 - The issue is not observed If I copy/paste files from `template/*` to src. - The issue is (usually) not observed if I use other text editor - `gedit`. Or if I also touch files (using `touch -m`). (Sometimes touch doesn't help either - that's more subtle, I am not sure how to consistently reproduce yet.) Sometimes refresh of output.css happens when I use `vim` too but it's quite rare (and is after some modifications of file outside of vim as well). --- Steps to reproduce - based on the GithHub repo above: - start tailwindcss --watch (e.g. via `npx pm2 start ecosystem.config.js`) - Modify `src/tailwind.css` copy-pasting the content of `templates/tailwind.css.2` using`vim`. - Similarly modify `src/index.html` (using index.html.2) - What happens is that in output.css I only have `btn-cool-1` but not `btn-cool-2`. I uploaded the state of the files to branch `topic/after-change-using-vim` in the same github repo. I included some `stat` outputs in case that matters. If I switch the order of modifying `tailwind.css` and `index.html` and I edit `index.html`
[ServerErrors][TypeScript] 5.1.0-dev.20230417
The following errors were reported by 5.1.0-dev.20230417 Pipeline that generated this bug Logs for the pipeline run File that generated the pipeline This run considered 200 popular TS repos from GH (after skipping the top 0). <details> <summary>Successfully analyzed 187 of 200 visited repos</summary> | Outcome | Count | |---------|-------| | Detected interesting changes | 158 | | Detected no interesting changes | 29 | | Git clone failed | 1 | | Unknown failure | 12 | </details> Investigation Status | Repo | Errors | Outcome | |------|--------|---------| |adonisjs/core|1| | |airbnb/react-sketchapp|1| | |airbnb/visx|1| | |akveo/ngx-admin|1| | |alibaba/ice|1| | |angular-ui/ui-router|1| | |angular/angular-cli|1| | |angular/angular|1| | |angular/components|1| | |ant-design/ant-design|1| | |apache/echarts|1| | |apache/superset|1| | |apollographql/apollo-client|1| | |apollographql/apollo-server|1| | |appwrite/appwrite|1| | |AykutSarac/jsoncrack.com|1| | |baidu/amis|1| | |balena-io/etcher|1| | |basarat/typescript-book|1| | |BrainJS/brain.js|1| | |BuilderIO/qwik|1| | |chakra-ui/chakra-ui|1| | |cheeriojs/cheerio|1| | |codex-team/editor.js|1| | |colinhacks/zod|1| | |compiler-explorer/compiler-explorer|1| | |conventional-changelog/commitlint|1| | |conwnet/github1s|1| | |darkreader/darkreader|1| | |date-fns/date-fns|1| | |directus/directus|1| | |discordjs/discord.js|1| | |Eugeny/tabby|1| | |excalidraw/excalidraw|1| | |expo/create-react-native-app|1| | |facebook/docusaurus|1| | |faceb
Decimal128 being read as new Decimal128("#") instead of the number
Prerequisites - [X] I have written a descriptive issue title Mongoose version 7.4.2 Node.js version 20.2.0 MongoDB version 1.42.1 Operating system macOS Operating system version (i.e. 20.04, 11.3, 10) Sonoma 14.2.1 Issue I'm trying to use a double/float data type for example (rev: 1.2), when I was using Number, mongoose would write it as an int so I've switched to using Decimal128 which would be better for our long term goals but I can't get rid of "new Decimal128". I'm open to whatever will let us use decimals and really would love to keep it simple. For instance rev 1.2 was being written as 1, and now that I've switched to Decimal128 it's reading it from the database (console.log on read) as: [code block] Schema: [code block] Database stores it as: [code block] I've been trying all sorts of different things but I can't manage to get mongoose to read from the MongoDB without the "new Decimal128" part of it. I've tried parseFloat, v.getDecimals and not using getters and setters. Thanks in advance for any help. MongoDB version for MongoDBCompass
Transient read failure may cause permanent failure to watch file
V3.1.18 Tailwind CLI, Visual Studio 2022 as editor. Node v14.18.1 Chrome Window 10 (No Docker or WSL) This issue is a very close relative of #7759, but I think it might be quite specialised so I don't want to pollute that one. I have a rather odd web project, which has a single HTML file. So the content section of tailwind.config.js looks like this: [code block] I run a tailwind CLI watcher with a command like this: [code block] I am suffering from the problem described in #7759 where the watcher stops watching after a while - anywhere between almost immediately and after lots and lots of successful rebuilds. By using the "Process Monitor" utility to observe the filesystem activity on the index.html file, I have observed that when Visual Studio (devenv.exe) is saving index.html, it goes through a rename/replace process which means there is a window of time in which the index.html file does not actually exist. It appears that node.exe (i.e. Tailwind) sometimes tries to read the file during this window and finds it to be missing. This apparently causes Tailwind to stop watching that file. The blue selected line in the image is Node getting a file-not-found failure doing a CreateFile (it's actually an open-to-read) on index.html in the middle of devenv doing a rename dance. I think that's a smoking gun. If I change the content file specification to be a wildcard, then my first impression is that things are much more robust: [code block] So: 1. Is it possible/
MongooseError: Operation `.deleteOne()` and `.deleteMany()` buffering timed out after 10000ms
Do you want to request a feature or report a bug? Bug What is the current behavior? Getting MongooseError timeout errors. I have not changed my code, or updated anything and I keep getting this timeout error. I exported my database and ran the same master branch with the same database on another PC and I do not get the error. If the current behavior is a bug, please provide the steps to reproduce. [code block] What is the expected behavior? Simple connection to mongodb, with the console log of "Successfully connected to MongoDB" What are the versions of Node.js, Mongoose and MongoDB you are using? Note that "latest" is not a version.* v16.13.0 node.js, v5.13.12 MongoDB Community Server 5.0.3 (current) Error: [code block]
Performance of async printers (was: Adopt `swc` parser?)
I don't know how faster can it be. The parser is not the really problem slowing us down, but should be faster. Hope we can rewrite our print in Rust? Maybe?
[BUG]: drizzle-kit push:mysql throws error with only connectionString
What version of `drizzle-orm` are you using? 0.26.1 What version of `drizzle-kit` are you using? 0.18.1 Describe the Bug When I try to migrate (push) my schema to my DB it throws an error `Error: Either `connectionString` or `host, port, etc.` params be provided in config file`. [code block] [code block] However I specified the connectionString... Am I doing something wrong here? Expected behavior It should push to db if I declared connectionString Environment & setup _No response_
users get unfixable (and inaccurate) type errors when using go-to-source for openai library code
Confirm this is a library issue and not an underlying OpenAI API issue - [X] This is an issue with the library Describe the bug simply adding the new `openai` package to my project causes all sorts of type errors when I cmd+click on into the OpenAI source code from my project <img width="1233" alt="CleanShot 2023-08-24 at 17 24 42@2x" src="https://github.com/openai/openai-node/assets/531504/454f7fd8-2e54-4545-bc38-a7181bf613bb"> To Reproduce See above. OS macOS Node version n/a Library version 4.2.0
Forbidden Runner version v2.317.0 is deprecated and cannot receive messages
This happened to us on 2.317.0, which is the latest version at time of writing: [code block] It happened twice. Timestamps in UTC. past occurence: https://github.com/actions/runner/issues/3366#issuecomment-2204514441
Could not import faiss-node (NextJS) when loading from python
Hi, I know this is a duplicate of: https://github.com/langchain-ai/langchainjs/issues/2107 However, in that issue it says that this has been resolved. While I'm on the latest release: 0.1.2 Which should have the fix for this available here: https://github.com/langchain-ai/langchainjs/pull/2178 My issue is the following: https://github.com/langchain-ai/langchainjs/issues/2107#issuecomment-1891106038 For reference, I'll post it below: Hi there, I'm getting the same type of error message in my console when I try to: [code block] knowledge is a folder in the root folder that includes 2 files: [code block] I am using the following to see whether my API route in nextjs can reach the files: [code block] this logs the actual filenames, so I know they're there... I'm getting the following error message in my console: [code block] I'm running this on windows with [code block] I've already tried installing the package, but I have no clue why my nextjs isn't importing the files... My node version is 20.10.0 Is there anything I can do to get this issue sorted? It says read properties of undefined (reading 'indexOf') This to me indicates it can not read the ./knowledge folder with files for some reason. But I haven't been able to figure out why yet. I could be totally wrong here though.
Vite and Docker
Describe the bug vite and docker dont seem to work well together every time i develop with both the browser reloads every minute. The browser reloads up to five time per initial load . Also the server crashes at random times during development . Reproduction https://github.com/louiss0/vue-2-template System Info [code block] Used Package Manager npm Logs _No response_ 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/vue-next instead. - [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
Uncaught TypeError: Cannot read property 'ToolItem' of undefined
Describe the bug Throw error `Uncaught TypeError: Cannot read property 'ToolItem' of undefined`. And I've found an error in the bundle of @antv/x6 (ToolsView is used before definition): [code block] Reproduction Please check this demo: vite-x6.zip Without `src/init.tsx:66` and `src/init.tsx:6`, it works as exprected. System Info Output of `npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers`: [code block] Used package manager: yarn Logs [code block] --- Before submitting the issue, please make sure you do the following - [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] Provide a description in this issue that describes the bug. - [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/vue-next instead. - [x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[BUG] npm incorrectly assumes existence of root-owned files on Termux
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 On Termux, npm seems to incorrectly assume the existence of files owned by root in the `.npm` directory when trying to either check the outdated global packages, installing a package, or updating a package; nothing in Termux is root-owned by default (and your device must be rooted to even have anything owned by root). This behavior has started occurring since npm v8.12.0. Example: [code block] As mentioned, this can also occur when trying to install or update a package (doesn't matter if it's global or local). Some others seems to be experiencing the same issue: https://github.com/npm/cli/issues/5025, and https://github.com/npm/cli/issues/4451#issuecomment-1152885628 Expected Behavior The expected behavior is for npm to work without assuming the existence of root-owned files that doesn't actually exist, basically to not throw the aforementioned error when checking for outdated global packages, installing/updating global or local packages. Example: [code block] Steps To Reproduce 1. Download, install, and launch Termux from it's official website. 2. Update all installed packages by running `apt update && apt upgrade -y`. 3. Install the latest Node.js LTS release (it doesn't have to be LTS, but for the sake of the example) which bundles npm as well by running `apt install nodejs-lts -y`. 4. Up
HNSW + dead tuples: recall loss/usability issues
This issue is a follow-up on this discussion in #239. Scenario: User sets `ef_search` to 10 expecting to get top-10 results back. But the top-10 results in the HNSW index happen to be dead tuples (due to updates & deletes), then the query will return 0 results. While this doesn't impact things like ann-benchmark, it will impact more realistic usecases where applications update/delete data. Desired Behavior: HNSW index returns the top-10 results where the tuples aren't dead to avoid causing significant recall loss - e.g. in the scenario above, recall would be 0%. Note that ivfflat has the desired behavior. I can see some potentially ugly workarounds: 1. users always performs a vacuum on every update/delete con: resource intensive con: complexity on application logic 2. users performs more frequent periodic vacuum con: should theoretically minimize the problem but offers no bounded guarantees, user can still hit the above problem between the periodic vacuums 3. users can specify higher `ef_search` con: how will a user know what `ef_search` to specify? * con: `ef_search` can be specified up to 1k, which should theoretically minimize the problem but also offers no bounded guarantees - e.g. user can still hit the above problem when the top-1k results of a large dataset in HNSW are dead And I think the ugly workarounds will fall apart especially for larger datasets, so having a principled fix in the HNSW index would help real-world users. Thoughts?
[BUG] npm fails install of any packages - TAR_BAD_ARCHIVE
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 `npm` fails to install any packages, downloading any dependency related to `eslint` causes `TAR_BAD_ARCHIVE` error. Here's what I tried: - clean npm caches - doesn't help! - `npm audit verify` , `npm audit fix`, `npm audit fix --force` - delete & reinstall npm (various attempts with various protocols for deletion and installation) - tried to disable `eslint`, but react app creation scripts contain it by default - tried to upgrade `eslint` version, but I get the same `TAR_BAD_ARCHIVE` when `eslint` is being installed Here are the failed downloads from the logs after running `npm install`, `npm init @eslint/config@latest` or any other package install that has dependencies on `eslint`: [code block] [code block] Expected Behavior The packages should be installed, and .tgz archives normally downloaded. Steps To Reproduce _No response_ Environment - npm: 10.9.0 - Node.js: v22.11.0 - OS Name: MacOS Sonoma 14.5
`process.env`, `globalThis`, and `typeof process`
This is a writeup to discuss this problem in the GraphQL-WG and the GraphQL-JS-WG. Please give feedback in either of those meetings, or here in the issue, until the next GraphQL-JS-WG meeting, where we want to make a final call on this issue. Last year, #3887 was released which changed the dev check in `src/jsutils/instanceOf.ts` from [code block] to [code block] shortly followed by #3923, which changed it to [code block] as some bundlers were choking on the optional chaining syntax. Since then, various issues and PRs have been opened to change into various other forms. I'll try to give an overview over problems, potential solutions and their shortcomings here so we can decide on a way forward. Problems: 1. accessing `process.env.NODE_ENV` directly There is a bunch of environments (e.g. ESM in the browser), where accessing `process.env` directly just crashes, since `process` is not a variable. 2. accessing `globalThis.process.env.NODE_ENV`: bundler replacement Some bundlers do a string replacement of `process.env.NODE_ENV`, which lead to the code being replaced by invalid JavaScript like `globalThis."production"`. (Afaik, most of these have been reported in the upstream bundlers at this point in time and they have fixed their regular expressions) 3. accessing `process.env.NODE_ENV` or `globalThis.process.env.NODE_ENV` while testing for `process`, without checking if the `env` property is set: DOM elements with the id `process` If a DOM element with the `id` `proc
Unable to run npx tailwindcss init with TailwindCSS 4.0.0: command not found
I am having issues installing the latest version of Tailwind! In my case, I’m not using Vite, but I encountered this problem after attempting to install the latest version of TailwindCSS in an existing project. Environment: • OS: macOS Sequoia Version 15.2 (24C101) • Node.js version: 18.17.0 • TailwindCSS version: ^4.0.0 Steps I took: Installed TailwindCSS using the command (and its installing the latest version: 4.0.0): npm install -D tailwindcss Tried initializing the TailwindCSS configuration: npx tailwindcss init Actual Behavior: sh: tailwind: command not found -- This error indicated that the tailwindcss package was not installed globally, but it actually was! Surprisingly, when I switched to an older version of TailwindCSS, the command worked as expected.
Getting multiple instances of graphql error despite only having a single version
I wasn't sure whether or not to make a new issue or comment on https://github.com/graphql/graphql-js/issues/594 but that one is so old I figured it would be preferable to start anew In my project I get the "ensure that there are not multiple versions of GraphQL installed in your node_modules directory" error despite having done so. yarn list output: [code block] and for posterity: [code block] My tech stack includes apollo-server-lambda and nexus-schema. Not sure if/how one of them could be behind this, but the issue only cropped up after switching from apollo-server-express to apollo-server-lambda. Nevertheless, it would seem that graphql-js is reporting this error erroneously as I have proven there is only one instance of graphql in my node_modules directory. exact error message: [code block] Link to my project repo: https://github.com/link2cory/portfolio-backend/tree/serverless a quick note: although it is not in the current version of my repo, I have tried making use of the resolutions yarn with exactly the same results. Plus the evidence I have provided above suggests to me that it should not be necessary based on my project dependencies. Please correct me if I am wrong in any of these assumptions!
[v4] importing tailwindcss/utilities breaks hmr
Im using: - tailwind v4.0.0-alpha.17 ( @tailwindcss/postcss ) - nuxt v3.12.3 - sass v1.77.8 The following code works perfectly: [code block] But whenever i try and import the utilities from tailwind like so: [code block] The HMR stops working, it does still say that the HMR got updated but it wont actually apply the changes to the front-end. Whenever i save my main scss file, the changes actually get applied.
DX: using `client` as the route name causes an error
Provide environment information [code block] Describe the bug I've created a route and named it `client` but I get this error when trying to use `trpc.useContext()` [code block] I could fix the issue by renaming it to `clientRoute` and the problem was solved Link to reproduction https://stackblitz.com/github/trpc/examples-next-minimal-starter To reproduce Create a route and name it `client`, This should trigger an error as shown in the video below: https://user-images.githubusercontent.com/56588770/216343859-4bd76863-845e-45bd-a664-0911b4ed0054.mov Additional information _No response_ 👨👧👦 Contributing - [ ] 🙋♂️ Yes, I'd be down to file a PR fixing this bug! <sub>TRP-54</sub>