Skip to content
This repository has been archived by the owner on Jan 26, 2019. It is now read-only.

Property 'a' must be of type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>' #341

Closed
jeffarese opened this issue Jun 13, 2018 · 2 comments

Comments

@jeffarese
Copy link

jeffarese commented Jun 13, 2018

Is this a bug report?

Yes

Can you also reproduce the problem with npm 4.x?

Yes. I first tried with 5.6.0, then with 4.2.0, then with 6.2.0

Which terms did you search for in User Guide?

Initial build, Failed to compile

Environment

  1. npm ls react-scripts-ts (if you haven’t ejected): react-scripts-ts@2.16.0
  2. node -v: v8.10.0
  3. npm -v: 5.6.0
  4. yarn --version (if you use Yarn): 1.7.0
  5. npm ls react-scripts-ts (if you haven’t ejected): react-scripts-ts@2.16.0 (again)

Then, specify:

  1. Operating system:
  • Antergos

  • Kernel: x86_64 Linux 4.16.13-1-ARC

  1. Browser and version (if relevant):
    Chrome Version 68.0.3440.15 (Official Build) dev (64-bit), but it's not relevant.

Steps to Reproduce

(Write your steps here:)

  1. create-react-app project-name --scripts-version=react-scripts-ts
  2. cd project-name
  3. yarn start or npm run start

Expected Behavior

It should compile the app.

Actual Behavior

(2248,13): Subsequent property declarations must have the same type.  Property 'a' must be of type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>', but here has type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>'.nchorElement>', but here has type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>'.

image

Reproducible Demo

@alex-ketch
Copy link

@jeffarese I've encountered the same warning before, and it was due to conflicting versions of @types/react or @types/react-dom.
You can check if that's the case by running yarn list @types/react* inside your project

@jeffarese
Copy link
Author

So what was happening is that I don't know why but there was a package.json and a node_modules folder in my home folder, and the npm run start was trying to use that (hence the /home/user/node_modules) instead of home/user/path-ro-repo/node_modules.

Deleting this package.json and node_modules (even them being outside the project folder) solved the issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants