All Issues
24,993 verified issues
[FEATURE] Do not remove node_modules on npm ci
What / Why I would really like to see a flag like `npm ci --keep` to do an incremental update on our buildserver as this would speed up our deployments a lot. Like suggested before on github and on the community. The last update was on the 7th of October that this was being reviewed by the cli team. Could someone post an update on this? :-)
Feature: Soft Delete
I would like to know your opinion on implementing Soft Delete in TypeORM. I would love to help doing this.
PostCSS plugin postcss-nested requires PostCSS 8
Describe the problem: When I upgraded Tailwind CSS to the version 2.0.1 inside my Next.js 10.0.2 (which should come with PostCSS 8, because Autoprefixer v10 works) project, it throw: [code block]
Define services which are not started by default
Users quite often define maintenance scripts, test suites, debugging systems in their Compose files which they don't want to run when they do `docker-compose up`. There should be some way of defining what services are started by default, but can be still be run manually by doing `docker-compose up servicename` or `docker-compose run servicename ...`. Possible solutions 1) Recommend users to use a separate Compose file 2) Add an option to services to make them not start by default 3) Add a top-level configuration option to define the default services 4) Add a concept of a thing like a service, but is just for one-off commands ("scripts", "tasks", etc...) (Please suggest others if you have ideas.) Data points: - https://github.com/docker/compose/issues/697 - https://github.com/docker/compose/issues/912 - https://github.com/docker/compose/issues/942 - https://github.com/docker/compose/issues/1439 - https://github.com/docker/compose/issues/1547 - #542 - "test" service in https://github.com/heroku/logplex/blob/master/docker-compose.yml - ~~@cpuguy83: "I've got a little helper service in my compose yaml that injects a bunch of stuff into redis for hipache, which of course exits when it is done. Can't use `compose up` w/o the `-d`"~~ this is fixed now that we don't exit from `compose up` until all services have exited.
Suggestion: Regex-validated string type
There are cases, where a property can not just be any string (or a set of strings), but needs to match a pattern. [code block] It's common practice in JavaScript to store color values in css notation, such as in the css style reflection of DOM nodes or various 3rd party libraries. What do you think?
How should we set up apps for HMR now that Fast Refresh replaces react-hot-loader?
Dan Abramov mentioned that Devtools v4 will be making `react-hot-loader` obsolete: https://twitter.com/dan_abramov/status/1144715740983046144?s=20 > Me: > I have this hook: > [code block] > But HMR has always worked completely without it. Is this now a new requirement? > Dan: > Yes, that's what the new mechanism uses. The new mechanism doesn't need "react-hot-loader" so by the time you update, you'd want to remove that package. (It's pretty invasive) I can't see any mention of HMR in the Devtools documentation, however; now that `react-hot-loader` has become obsolete (and with it, the `require("react-hot-loader/root").hot` method), how should we set up apps for HMR in: React DOM apps React Native apps * React custom renderer apps I'd be particularly interested in a migration guide specifically for anyone who's already set up HMR via `react-hot-loader`. Also, for HMR, does it matter whether we're using the standalone Devtools or the browser-extension Devtools?
React Native 0.62.* [TypeError: Network request failed] on file upload
Please provide all the information requested. Issues that do not follow this format are likely to stall. Description After upgrading from 0.61.4 to 0.62.0 the app will not upload files anymore from Android (all other requests are working fine) React Native version: 0.62.0 Steps To Reproduce 1. Install a fresh ReactNative app via CLI 2. Upload a file to the emulator 3. Try to upload a file using `fetch` [code block] Expected Results The request should reach the server to upload the file Snack, code example, screenshot, or link to a repository: https://snack.expo.io/01W!bybf_ [code block]
Cannot set property EntityManager of #<Object> which has only a getter
Issue type: [x] bug report Database system/driver: [x] `postgres` TypeORM version: [x] `latest` Steps to reproduce or a small repository showing the problem: [code block] Somehow getting this random error now and have. Literally tried rolling back my code and everything. Any suggestions where to look?
Support for NVIDIA GPUs under Docker Compose
Under Docker 19.03.0 Beta 2, support for NVIDIA GPU has been introduced in the form of new CLI API --gpus. https://github.com/docker/cli/pull/1714 talk about this enablement. Now one can simply pass --gpus option for GPU-accelerated Docker based application. [code block] As of today, Compose doesn't support this. This is a feature request for enabling Compose to support for NVIDIA GPU.
Official TypeScript definitions
Official TypeScript definitions
Error: Unable to resolve module `./debugger-ui/debuggerWorker.cff11639.js` from ``:
Please provide all the information requested. Issues that do not follow this format are likely to stall. Description Please provide a clear and concise description of what the bug is. Include screenshots if needed. Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html React Native version: [code block] Steps To Reproduce Provide a detailed list of steps that reproduce the issue. 1. run `npx react-native init Blah --template react-native-template-typescript` 2. run `npx react-native start` 3. run `npx react-native run-android` 4. Tell app to use debug mode 5. See exception: [code block] Expected Results I wouldn't get this error.
Request params are not getting merged with instance params
Describe the bug Specific request params do not get merged with the instance default params. To Reproduce [code block] [code block] What happens is that the request param object overrides the instance default param object. The instance no longer has a query param of `q`. Expected behavior According to the docs, all configuration options are merged. https://github.com/axios/axios#instance-methods I expected request to contain both `q` and `page` params. This is also how it was working in version 0.18.0, which is how I noticed. Environment: - Axios Version: 0.19.0 - OS: 10.14.5 (18F132) - Browser: Node Express, and Chrome - Browser: Node 10.15.0, Chrome Version 74.0.3729.169 (Official Build) (64-bit)
[BUG] npm update --global fails: npm ERR! global requires an add or rm option
Current Behavior: [code block] Expected Behavior: Before v7.0.0, running `npm update --global` would update all the packages installed globally which are outdated. Steps To Reproduce: Install an outdated global package, and try to update all the packages. Environment: - OS: Ubuntu 20.04.1 - Node: 12.19.0 - npm: 7.0.0
package 404 not found
What / Why Your package manager couldn't get any packages. (404 not found) When Now Where npm public registry How n/a Current Behavior 404 not found
Add sorting to Open Editors list
This could be simply optional alphabetic sorting. As it stands when you have lots of files open it can be hard to match up files that are associated (e.g. circus.component.js and circus.component.html) without the tedious task of manually dragging them into order.
Road to Typescript
This is an issue is to discuss our plan to convert this library to TypeScript. Note: We will still continue to provide full Flow typings in the same package. This effort is in line with the ongoing conversion of GraphQL IDE packages (GraphiQL, GraphQL LSP, etc.): https://github.com/graphql/graphiql/tree/convert-to-ts Note this decision is not related to the technical aspect of Flow vs TS. GraphQL.js has complete Flow coverage and it is excellent for ongoing maintenance. But our goal is to increase the number of active contributors and by switching codebase to TypeScript we hope to make the codebase feel more familiar and easy to contribute to. Big thanks to @JacksonKearl from Apollo team for making PoC for such conversion and exploring different conversion strategies. Before we start discussing the action plan here is a few important points: `14.x.x` is stable release so we shouldn't do any potentially breaking things in this release. We need to do `15.0.0` anyway since it becomes hard to maintain support for Node6 since ESLint and other projects stop supporting it. Plus it allows us simply remove all deprecated stuff that was scheduled for removal in this release. Even after we release `15.0.0` we will still need to support `14.x.x` as a branch and backport all critical or security-related bugfixes until `16.0.0`. Giving these constraints here is a plan I want to propose: - [x] 1. Freeze all non-critical merges for the duration of this conversion - [x] 2. I copied al
Icon change for macOS Big Sur
macOS Big Sur brings macOS' system icons all with square corners, and some 3rd party developers including Adobe are converting their app icons to match up with these system icons. Are there any plans for VS Code? <img width="500" alt="Screen Shot 2020-06-25 at 12 12 49" src="https://user-images.githubusercontent.com/17576065/85691454-31ef1080-b6dd-11ea-9e72-9a7e709a19d4.png">
Integrated Terminal Lags Intermittently
- VSCode Version: 1.48.2(macOS Stable) - OS Version: macOS Big Sur 11.0 Beta (20A5354i) (Public Beta Release 2) Steps to Reproduce: 1. Open Terminal 2. ~~Spam random keys until lag is experienced~~ Press enter, then continuously type (anything) for about 2 seconds. 3. Experience a very long stutter Does this issue occur when all extensions are disabled?: Yes This occurs on a public beta build of macOS 11. I've confirmed the same issue on two different MacBook Pro's on the same OS version, and same VS Code version. Attached is a performance profile. You can see the spike in the integrated terminal response time at around 23000ms - 24000ms Profile-20200826T124154.json.zip
Google native ads integrated into a Flutter widget tree
This comment discusses the different ways we are considering addressing this issue, and provides links to more specific issues that cover specific steps towards this issue: https://github.com/flutter/flutter/issues/12114#issuecomment-505633342 We are working on some of these today. Please see the individual bugs for details. ---- Both Firebase (AdMob) and Facebook support a "Native Ads" format: https://developers.google.com/admob/android/native https://developers.facebook.com/docs/audience-network/native-ads/ Native ads are rendered inline with the app's content, with rendering and formatting (colors, fonts) controlled by the app itself.
key sequence to detach from `docker-compose up`
this has been topic in #291, however i want to make aware of this feature request a little more . i vote for a key-sequence that you can use to detach from `docker-compose up` without stopping all containers (i.e. when you forgot to pass `-d`). There seems to be a key-sequence for attached docker-containers (`Ctrl-p` `Ctrl-c`). It seems plausible to reuse this in docker-compose.