All Issues
24,993 verified issues
Provide live preview of HTML like Adobe Brackets
You should implement a live preview interface with all browsers
Can I help get tinyint or half branches released?
Is there more to do on the `tinyint` or `half` branches to get them released or are they ready to be put into `0.5.1`? If there is more to do for them, let me know and I'll see if it's something I could take care of (e.g.: code, docs, tests, etc).
MongoDB $ne key collision in object literal silently uses wrong operator
In a MongoDB query, writing `{ status: { $ne: null, $ne: '' } }` creates a JavaScript object with a duplicate key. The second `$ne` silently overwrites the first. The query only filters out empty strings, never null values. TypeScript does not warn about duplicate keys in object literals by default. The correct approach is `$nin: [null, '']`.
[FEATURE]: Prisma's `updatedAt` behavior. `onUpdate` API suggestion
Describe what you want Prisma has awesome feature such as declaring a column with `@updatedAt` which updates that column with a new timestamp every time the record updates. Instead of suggesting to add something similar like just `updatedAt` alternative, what if you provide a more flexible `onUpdate` method when declaring columns in schema so we can do something like this: [code block] The idea is that this method accepts a callback function that returns a new value for the column. The callback function is invoked every time the record updates. The basic example is to use it for timestamps on `updatedAt` columns, but it can be used for anything since the new value will be the one returned by the callback. In general, when the record updates, we can find out which columns were updated, old values and new values. Maybe, this data can be accepted by `onUpdate` callback like [code block] Or any other better API for this.
[FEATURE]: Dependency to deprecated package `@esbuild-kit/esm-loader`
Describe what you want `@esbuild-kit/esm-loader` was recently marked as deprecated. It might be a good time to update the dependencies to this library.
[BUG]: error: type "serial" does not exist
What version of `drizzle-orm` are you using? 0.30.8 What version of `drizzle-kit` are you using? 0.20.16 Describe the Bug After generating a migration with drizzle-kit, running `drizzle-kit push:pg` results in `error: type "serial" does not exist` Schema: [code block] Migration: [code block] Full error: [code block] Expected behavior Expect migration to be run and table alteration to complete successfully. Environment & setup macOS 14.4.1 Vercel Postgres: PostgreSQL 15 @vercel/postgres: 0.8.0
Missing TypeScript Nodes (2)
See https://github.com/prettier/prettier/issues/1480#issuecomment-299230108 for up to date info There are still some nodes missing, but we're getting there :) Missing printer implementation: [x] "TSAsyncKeyword" (#1483) [x] "TSDecorator" (#1488) [x] "TSExportKeyword" (#1483) [x] "TSNamespaceFunctionDeclaration" (#1483) [x] "TSProtectedKeyword" (#1483) [x] "TSPublicKeyword" (#1483) [x] "TSHeritageClause" (#1483) [x] "TSExpressionWithTypeArguments (#1483) Missing in `typescript-ast-nodes.js`: [x] "TSParameterProperty" [x] "TSTypeParameter" There are also some nodes printed incorrectly, probably because some optional keywords aren't printed which should be easy to fix. And there are errors where we're trying to access properties on undefined, those are probably because TypeScript types are missing in `typescript-ast-nodes.js` or because we expect optional stuff to just be there. The raw output of running prettier of the TypeScript test suite can be found here (careful, it's big). If anyone wants to help with this drop a line here, so we don't duplicate the effort. see #1422 #13 #1306 /cc @azz
Webhook signature verification and bodyParser.json issue
If you use in your express app `bodyParser.json()` for all routes, and then have a dedicated route for stripe's webhook, then the second call to `bodyParser.json({verify: ...})` as done in the example has no effect. I have the following code: [code block] The StripeRoute is defined exactly as the example. Unfortunately it doesn't work. Only if I comment out the first call to `bodyParser.json` does it work. Which mean that I cannot have a call to `bodyParser` just for my route, I need to add the `verify` function my top call to `bodyParser.json` and to avoid having to pay for the conversion all the time check for the Url to match my stripe route. Maybe the doc should reflect that, and if it is supposed to work then some guidance as it doesn't for me. Thanks!
Add --exclude to docker-compose up
I have a Compose file with 10 services. I want to start only 8 of them. I can do `docker-compose up srv1 srv2 srv3 srv4 srv5 srv6 srv7 srv8` but it would be better to do `docker-compose up --exclude srv9 srv10`. Useful syntactic sugar IMO.
Add support to transpile modules inside node_modules
Now some of us ships NPM packages (specially components) written in ES2015 without transpiling them. That's a pretty good thing specially if they are gonna used in a project like Next.js or CRA (which does transpiling). They offer benefits like: No need to transpile before shipping to NPM Get the benefit of Webpack 2's tree-shaking But we can't do this now we exclude everything inside node_modules from babel transpiling. So, here's the proposed solution. We have an entry in `next.config.js` to include modules which needs to go through babel. See: [code block]
React Redux state shows stale user data after profile update — backend not refetched
After a successful PUT /user profile update, the Redux store still shows the old data. The component builds the new state from the form values instead of re-fetching from the API. When the user navigates away and returns, stale data reappears. The pattern of dispatching a local state update instead of fetching fresh server state is the root cause.
Adding GA script tag?
Hi there! I am currently converting my website to a next.js project and can't figure out on how to add the Google Analytics script tag to the page. Any thoughts? Cheers, Robin
"EMFILE - too many open file" error
Previous issue: #3249, #10706 This is a meta-issue to gather all reports about the following error: [code block] This is a very tough issue to solve because it happens randomly. It is caused by having too many files open _on the whole machine_ (not just the `serverless` process). A possible root cause could be synchronous usage of the `fs` API. A solution might be to use `graceful-fs` and/or the async API to access the filesystem. We use `graceful-fs` and reduced the use of sync calls in Serverless Framework to a minimum, but some plugins might not. We're trying to identify which plugins might cause the issue. Workarounds This isn't ideal, but it is possible to increase the limit of files open on Linux and macOS with `ulimit` (https://stackoverflow.com/a/21070580/245552), but not on Windows. If you have information about more workarounds, please post them here and we'll update the issue. How to help? - Add a 👍 on this issue (so that we can estimate the impact) - Investigate if some plugins might benefit from using `graceful-fs` and/or async filesystem calls - Fill the following form and post it as a comment: [code block] Let's try and see if there's a pattern (e.g. a plugin that comes up often).
TypeError: crypto.hash is not a function
Describe the bug I simply installed a React TypeScript project using pnpm create vite and tried to run it, but encountered the following error. I'm on a Windows environment and using Node.js version v20.9.0. This issue didn't occur before, so it seems to be related to the recent update to Vite version 7.0. [code block] Reproduction . Steps to reproduce _No response_ System Info [code block] Used Package Manager pnpm 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 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.
Change HTML/JSX formatting to have one attribute/prop per line
Similar to what was done for #3847 I think it best to break some of the discussion from #3101 into a new issue that people can 👍 or 👎. I'm proposing that for HTML and JSX to have Prettier always have one attribute/prop per line (and thus not respect the developer's original preference). Code would then be formatted as shown below. This is in contrast to the current behaviour where we fit as much as possible with the print-width. Expected behavior: [code block] This suggestion for one attribute/prop per line was proposed several times in the discussion of #3101 but I think it is clearer if this is pulled into it's own proposal. The original proposal in #3101 is that Prettier would add an option to preserve original formatting which, while I agree with the author with the style that they want, I don't think a) an option, nor b) preserving original formatting follows the aims for Prettier (see also #2068). Instead I think the aims of #3101 are better served by this proposal to ignore the print-width and always place attributes/props on new lines (assuming that there is more than one). This style appears to be the most common formatting for Angular, Vue and React from what I can tell. It style appears to be the style enforced by the rules: React: jsx-max-props-per-line which Airbnb set to to 1 in their style guide Vue: max-attributes-per-line which has a default to 1.
Docker buildx exec format error on Apple Silicon when targeting linux/amd64
Building a multi-platform Docker image with `docker buildx build --platform linux/amd64` on an Apple Silicon Mac (M1/M2/M3) fails during the build step with 'exec format error'. The amd64 platform requires QEMU emulation or Rosetta to run x86 binaries on ARM hardware. Without proper setup, the build starts but fails when it tries to execute any amd64 binary inside the container.
npm v7 does not install linked packages dependencies
Current Behavior: npm v7 does not install linked local packages dependencies. Expected Behavior: In npm v6 the dependencies of a local linked package are installed. This means that if `app` has `my-local-pkg` as a dependency, running `npm install` generates `app/node_modules` folder and also `my-local-pkg/node_modules` (with its dependencies). In npm v7, however, only `app/node_modules` is generated. Steps To Reproduce: I created the following repository to illustrate it. The `README.md` has the instructions on how to reproduce it. Simplified, the steps are: 1. Add the following folder structure: `./app` and `./my-local-pkg`, each with their own `package.json` 2. Include this in the `./app/package.json`: [code block] 3. Include this in the `./my-local-pkg/package.json`: [code block] 4. Go to `./app` and run `npm install`. npm version 6 produces: [code block] while npm version 7 produces: [code block] Compare the two outputs, npm v7 does not install `my-local-pkg` dependencies, there is no `./my-local-pkg/node_modules` folder generated. Environment: npm v7.1.2
Allow configuration for using px instead of rem
I don't really know why the previous issues #800 and #968 got closed without a real response. There are as much valid use cases for using `rem` as there are for using `px`. Lets take the simple example of a website builder which has two seperate user interfaces. One that includes all the App Components designed using Tailwind, and another which includes the user generated content. If I would like to scale up or down only the user generated content area of the UI by modifying the `font-size: 16px` property on the body element, it only works if the rest of the user interface has a fixed sizes using `px` instead of `rem`. If everything uses `rem` I can't change the size of things independently of each other.
Support --user option in "docker-compose up"
I need to pass `--user` option to run orchestrated containers under my own UID. This is mostly because of mounted host volumes, and I'd like the dockerized app to generate files owned by me, not the root. With `docker-compose up`, this is not possible, at least not directly. Right now I'm using a crazy workaround: [code block] which is suboptiomal, to be gentle.
[BUG] Overrides are not updating after running npm install
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 After updating the overrides, `npm install` is not updating the `package.lock` or `node_modules`. To make it work I had to remove both `package.lock` and `node_modules`, then the overrides have been applied. Expected Behavior Change in `overrides` should update `package.lock` and `node_modules` after running `npm install` Steps To Reproduce 1. Add a dependency 2. npm install 3. Add override 4. npm install Environment - npm: >=8.3.0 - Node.js: 16.13.2 - OS Name: macOS 12 - System Model Name: - npm config: [code block]