All Issues
24,993 verified issues
Column type for UserModel#userId is not defined and cannot be guessed. Make sure you have turned on an "emitDecoratorMetadata": true option in tsconfig.json.
Column type for UserModel#userId is not defined and cannot be guessed. Make sure you have turned on an "emitDecoratorMetadata": true option in tsconfig.json. Also make sure you have imported "reflect-metadata" on top of the main entry file in your application (before any entity imported).If you are using JavaScript instead of TypeScript you must explicitly provide a column type. ExceptionsManager.js:76 Module AppRegistry is not a registered callable module (calling runApplication) package.json `{ "name": "janmanch", "version": "0.0.1", "private": true, "scripts": { "start": "node node_modules/react-native/local-cli/cli.js start", "test": "jest" }, "dependencies": { "@babel/runtime": "^7.1.2", "@ldn0x7dc/react-native-view-pager": "0.0.9", "npm": "^6.1.0", "react": "16.3.1", "react-native": "0.57.0", "react-native-bottomsheet": "^1.9.0", "react-native-datepicker": "^1.7.2", "react-native-device-info": "^0.21.5", "react-native-elements": "^0.19.1", "react-native-flexi-radio-button": "^0.2.2", "react-native-localization": "^1.0.10", "react-native-permissions": "^1.1.1", "react-native-splash-screen": "^3.0.9", "react-native-sqlite-storage": "^3.3.6", "react-native-swiper": "^1.5.13", "react-native-vector-icons": "^4.6.0", "react-navigation": "^2.3.1", "realm": "^2.8.4", "reflect-metadata": "^0.1.12", "remove": "^0.1.5", "typeorm": "^0.2.7" }, "devDependencies": { "@bab
TypeError: Cannot read properties of undefined (reading '700')
What version of Tailwind CSS are you using? "tailwindcss": "^3.0.1", What build tool (or framework if it abstracts the build tool) are you using? "postcss": "^8.3.11", Angular 13 , What version of Node.js are you using? node : v16.13.0 What browser are you using? Chrome, What operating system are you using? Ubuntu 20.04 Describe your issue after I update Tailwindcss on my angular 13 project I get the below error when I try to run the project I try to look into these files I found that the gray color has problems or is even not found also I have a custom tailwind.config `TypeError: Cannot read properties of undefined (reading '700') at module.exports ( node_modules/@tailwindcss/typography/src/styles.js:16:65) at value ( node_modules/tailwindcss/lib/util/resolveConfig.js:68:41) at node_modules/tailwindcss/lib/util/resolveConfig.js:132:24 at Array.map (<anonymous>) at Object.typography ( node_modules/tailwindcss/lib/util/resolveConfig.js:132:15) at node_modules/tailwindcss/lib/util/resolveConfig.js:155:57 at Array.reduce (<anonymous>) at resolveFunctionKeys (node_modules/tailwindcss/lib/util/resolveConfig.js:152:32) at Object.resolveConfig [as default] (node_modules/tailwindcss/lib/util/resolveConfig.js:224:16) at Object.resolveConfig [as default] (node_modules/tailwindcss/lib/public/resolve-config.js:15:39) ` here is the code where styles.js throw error: `module.exports = (theme) => ({ DEFAULT: { css: [
React native IOS Network Error
Describe the bug While making any post request using Axios package. I am getting a Network error. While the same API seems to be working perfectly fine with Android devices. It is not an issue with the API. To Reproduce Axios post request throws a network error message. If I make the call again inside the catch block then it works fine. [code block] Expected behavior It shouldn't through network error. What should be done to fix this behavior specifically for iOS devices/simulators. Environment - Axios Version [e.g. 0.19.2] - Additional Library Versions [e.g. React 16.9.0, React Native 0.62.2] Additional context/Screenshots N/A
[BUG] 429 Too Many Requests
What / Why > I'm getting E429 error When Everytime I run `npm ci` (since today at least) Where npm public registry Current Behavior The `npm ci` command returns E429 error (Too Many Requests) and doesn't complete packages installation Steps to Reproduce `npm ci` Expected Behavior It should install packages
Prisma 7 breaking changes to Prisma config file, and prisma schema
When upgrading to the latest version of prisma, i am getting issues with the config file saying engine:'classic' engine doesnt exist, then on project build i am getting an error saying the url in the db source block is deprecated but when removing it i get and error saying it is required to be added. <img width="662" height="137" alt="Image" src="https://github.com/user-attachments/assets/df2e918a-c541-4f55-8cca-3a573babbfc2" /> `npx prisma generate Loaded Prisma config from prisma.config.ts. Prisma schema loaded from prisma\schema.prisma Error: Prisma schema validation - (get-config wasm) Error code: P1012 error: The datasource property `url` is no longer supported in schema files. Move connection URLs for Migrate to `prisma.config.ts` and pass either `adapter` for a direct database connection or `accelerateUrl` for Accelerate to the `PrismaClient` constructor. See https://pris.ly/d/config-datasource and https://pris.ly/d/prisma7-client-config --> prisma\schema.prisma:11 | 10 | provider = "postgresql" 11 | url = env("DATABASE_URL") | Validation Error Count: 1 [Context: getConfig] Prisma CLI Version : 7.0.0` `{ "name": "ypay", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint" }, "dependencies": { "@aws-sdk/client-s3": "^3.856.0", "@prisma/adapter-pg": "^7.0.0", "@prisma/client": "7.0.0", "@prisma/extension-accelerate": "^2.0.2",
[v2] aws sso commands should allow opting out of automatically opening a browser
Is your feature request related to a problem? Please describe. I'm using a remote shell via SSH to a machine that has a GUI (macOS). When performing `aws configure sso` or `aws sso login` it dumps out the url and code to enter into a browser myself. However, the browser has already opened on the remote machine even though I cannot easily access it (nor want to). AWS does not allow me to use the url and code from the console in this scenario to login from my host machine because it was already used by the remote, unseen, browser. Describe the solution you'd like A CLI flag like `--no-browser` to avoid launching the default browser on the system, allowing me to use the url and code myself manually. Describe alternatives you've considered A CLI interactive prompt asking whether you'd like to open the default browser. I like this too, and think it should exist before automatically opening another window on my system, but I feel like CLI flags should always exist as well.
Library is not compatible with nextjs
Describe the bug I found several issue when i try to build a nextjs application using openai-node : - Typescript compiler option isolatedModules is set to true => Cannot use 'export import' on a type or type-only namespace when 'isolatedModules' is enabled.ts(1269) - use of "#" to define a private property not working To Reproduce create a sample application with : npx create-next-app@latest install openai-node write a simple chatCompletion in a page component Launch "npm run build" You will see errors on "checking validity of types" step. Code snippets _No response_ OS macOs Node version 16.8.x and more Library version 4.00 and more
Space after function keyword in anonymous functions
NOTE: This issue is raised due to confusion in #1139. This issue is _only_ about _anonymous_ functions: [code block] (Prettier currently does _not_ put a space there.) > 🗒 NOTE: This issue is _not_ about having a space after the function name: > > [code block] > > Space after function name is tracked in #3845! The key argument is: Consistency: This means that there's _always_ a space after the `function` keyword.
[BUG] npx behavior in CI environments
This isn't really a bug, but raising it to discuss the potential impact of changes to `npx` in CI environments. Current Behavior: [code block] `npx -y mocha` works to get the automatic install behaviour, but that would require users to update their CI scripts. Also, `npx -y mocha` errors in npm@6 with: [code block] I think that would complicate the logic required in CI scripts when running across multiple Node.js/npm versions. _Just using Mocha as an example. In Node.js, we use npx in our GH Actions configuration, which I suspect would be broken when GH Actions updates to use a version of Node.js containing npm@7._ Expected Behavior: - Unsure, but curious if there could be a workaround that removes the need for users to edit their scripts. Steps To Reproduce: - `npx <module>` in a CI enironment. Environment: - All CI environments /cc @MylesBorins @richardlau
on-destroy provisioners not being executed
Terraform Version `v0.9.2` Affected Resource(s) - digitalocean_droplet - provisioners (on-destroy) Terraform Configuration Files [code block] Debug Output https://gist.github.com/IOAyman/3e86d9c06d03640786184c1429376328 Expected Behavior It should have run the on-destroy provisioners Actual Behavior It did not run the on-destroy provisioners Steps to Reproduce 1. `terraform apply -var-file=infrasecrets.tfvars` 1. `terraform destroy -var-file=infrasecrets.tfvars` References Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example: - GH-13395
Invariant Violation: Module AppRegistry is not a registered callabel module (calling runApplication)
<img width="545" alt="Screenshot 2019-10-02 at 13 35 27" src="https://user-images.githubusercontent.com/5610758/66041369-fe020880-e519-11e9-8616-58da88177c0f.png"> Currently on React Native 0.61.0-rc.3, updating to 0.61.1 causes this issue. React Native version: [code block] Steps To Reproduce 1. Update the package.json values to use latest 0.61.1 (and other latest values pulled for a `react-native init`) 2. Run the project (`yarn && cd ios && pod install && cd .. && yarn start` + `yarn ios`) Describe what you expected to happen: The app should be running like on 0.61.0-rc.3. What major changes where made between the release candidate and 0.61.0 (also your website still show 0.60.0 as the latest version). Here is the source code changes between the two: https://react-native-community.github.io/upgrade-helper/?from=0.61.0-rc.3&to=0.61.1 Snack, code example, screenshot, or link to a repository: Can't be provided, production and private react-native init application.
[php] Provide html intellisense
In PHP files there is no html tags auto completion, please add. ----- EDIT 9/13/2018 @egamma: VS Code provides only basic support for PHP, but there are powerful PHP extensions available in the market place: - PHP IntelliSense - PHP Intelephence. This feature should be provided by these extensions (Intelephence actually already does support it). Please give these extensions a try and help to make them better by filing issues and pull requests. This issue has lost focus and turned into a discussion whether VS Code should provide PHP support out of box. However, as with many other language like C#, C++, Go, Python, Rust we do not want to bundle PHP with VS Code but rather rely on our great extension ecosystem. I´m therefore closing this issue.
outline-none doesn't work on button with focus in chrome
Hi, First of all, a big thank's for your work on Tailwindcss, it make coding css so cool again ! Maybe it's not a bug and you thought about this already, but it seems strange that outline-none doesn't set outline-none on focus too, on button element. I noticed that only on Chrome and only on buttons. If I want to remove outline on focus, I need to do : [code block] If not I see a big blue outline when the button is in Focus state. It seems that's its coming from normalize.css with : [code block] If I add `outline: none;` manually it's working too. Is that a normal behaviour ?
Suggestion: "safe navigation operator", i.e. x?.y
Current Status The TC39 proposal is now at stage 3 (🎉🎉🎉🎉🎉) Implementation is in progress You can expect this feature in TypeScript 3.7 We'll update here when it's available in a nightly build Holding off on Optional Call until its semantics are clarified at committee Open questions What special-casing, if any, should `document.all` get? -------- Cand other languages have syntax sugar for accessing property chains where `null` (or in our case, `undefined`) might be encountered at any point in the object hierarchy. [code block] Need proposal on what exactly we should codegen, keeping in mind side effects of accessors. _____ Edit by @DanielRosenwasser February 27, 2018: This proposal is also called the "null propagation" operator.
[FEATURE]: MSSQL dialect
Describe want to want Implement support for MSSQL dialect and popular drivers
[BUG] `npm ci` succeeds when `package-lock.json` doesn't match `package.json`
Current Behavior: `npm ci` does not fail when `package.json` doesn't match `package-lock.json` Expected Behavior: `npm ci` refuses to install when the lock file is invalid. Steps To Reproduce: 1. Manually bump a major version of a dependency in `package.json` 2. Run `npm ci` 3. It should fail but performs the whole installation npm@7 <img width="531" alt="image" src="https://user-images.githubusercontent.com/4542735/107903616-d4763f80-6f9d-11eb-8a64-345635eee6d3.png"> npm@6 <img width="746" alt="image" src="https://user-images.githubusercontent.com/4542735/107903652-ece65a00-6f9d-11eb-9401-d78aa3fc596f.png"> Environment: - OS: Mac OS - Node: 14.15.3 - npm: 7.5.4
[v4] "hidden" is not the last display utility anymore
What version of Tailwind CSS are you using? v4.0 Reproduction URL https://play.tailwindcss.com/1XH8TJa6s3 for v4 (element is shown) https://play.tailwindcss.com/Ajm578zcYz for v3.4.15 (element is not shown) Describe your issue The order of the `display` utilities has slightly changed in v4, putting `hidden` somewhere in the middle of these utilities by default (after `block`, but before `inline-block` or `inline-flex`), where in v3.4 it was at the end of all the `display` utilities. I have used TailwindCSS often like this: [code block] Then I remove or re-add the hidden class with Javascript, which worked fine in v3. In v4 this does not work with `inline-block` anymore (because `inline-block` comes after `hidden` in the generated CSS), while it does work with `block` (as it comes before `hidden`). I found the behavior better in v3.4, where `hidden` was assumed to be the preferred/overriding value (if set) of all the display utilities and comes last in the definitions. I could imagine many people used `hidden` in this way and will find the new order surprising.
axios doesn't see request headers that I set
Hi, I tried to make a CORS API post call using axios but I've been never able to do that because I must set headers to make a proper call however axios doesn't see the headers I set. For example, This is what I set as URL and Headers; [code block] The request is sent successfully so I don't write the code where I call axios. The problem is I couldn't set the headers. This is the request pic; This is my axiosConfig; Even if I set "Authorization", I don't know why it is not shown in my request.
NotificationResponseReceivedListener not called when app is killed
Summary I ran into problems while developing an app that has to respond to push notifications. I based this app on the expo notification snack that is found in the documentation. When trying out my app, the expo notification service works fine when an app is in the foreground or background, but does not trigger when the app is killed. I use the addnotificationresponsereceivedlistenerlistener method to handle notifications when the app is killed. I found a lot of issues about this problem that have already been closed. Unfortunately, the solutions/pull request in these issues don't solve the problem on my system. I therefore think this might be a bug that was introduced in version 42 of the expo SDK. Related issues - https://forums.expo.dev/t/push-notification-doesnt-open-specific-screen-when-app-is-killed-works-only-in-foreground-and-background/53890/5 - https://github.com/expo/expo/issues/13333 - https://github.com/expo/expo/issues/12954 - https://github.com/expo/expo/issues/12228 - https://github.com/expo/expo/issues/11933 - https://github.com/expo/expo/issues/11470 - https://github.com/expo/expo/issues/11340 - https://github.com/expo/expo/issues/10621 - https://github.com/expo/expo/issues/9968 - https://github.com/expo/expo/issues/6943 Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! managed What platform(s) does this occur on? Android SDK Version (managed workflow only) 42.0.1 Environment [code bloc
Warning: Prop className did not match.
Examples bug report Example name with-styled-components Describe the bug Also posted here: #2538 Using `css` prop introduced with styled-components v4 causes `Warning: Prop className did not match.`. To Reproduce Add any HTML element with `css` prop. Expected behavior Correctly styled rendering on the server side without any warnings. Screenshots System information - OS: Windows - Chrome - Version of Next.js: 8.1.0 Additional context Here is an example I created to demonstrate the issue: https://codesandbox.io/embed/jlwvwyy0ow Open this and refresh once the building is done: https://jlwvwyy0ow.sse.codesandbox.io/