Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Definition for rule '@typescript-eslint/consistent-type-assertions' was not found #198

Closed
nidble opened this issue Sep 22, 2019 · 8 comments

Comments

@nidble
Copy link

nidble commented Sep 22, 2019

Hi all,

As usual, I cloned the main repo and executed npm install/npm start. But unfortunately app crashed very soon reporting the error in the subject.

From this thread typescript-eslint/typescript-eslint#863 I fixed my local setup replacing into package.json react scripts lib: "react-scripts": "^3.1.2",.

I hope it helps. Thanks for your work.

@markerikson
Copy link
Collaborator

Ah... what repo did you clone, and for what purpose?

This is a library, not an app.

I'm kind of confused, and this doesn't seem like an actual issue with this library.

@nidble
Copy link
Author

nidble commented Sep 23, 2019

Whops! I'm sorry @markerikson.

My fault, the correct repo is https://github.com/markerikson/rsk-github-issues-example. What do you prefer? I can repost this issue on the correct repo, or considering the owner :), do I leave its to you?

@markerikson
Copy link
Collaborator

Hmm. I would be very surprised if there was a real problem with that repo - it's just a standard CRA project.

If you can consistently reproduce the problem, then maybe file an issue there, but I'm not sure there's really anything I can do about it. Also, I suggest trying yarn instead of npm.

@nidble
Copy link
Author

nidble commented Sep 26, 2019

Hi Mark, I tried with yarn and everythings works fine. Currently the "issue" is only with npm (6.9.0). The steps to get involved are quite simple: npm install && npm run start.

@markerikson
Copy link
Collaborator

Yeah, I really don't see anything actionable to do here. It's a plain standard CRA app, and installing the packages works with Yarn. If NPM is having problems, that's outside the scope, and I can't think of anything I could change to affect that.

@nidble
Copy link
Author

nidble commented Sep 27, 2019

Yes, sure. My comment was only to give you an insight about. And a reference to other people that meeting this issue. Thanks.

@markerikson
Copy link
Collaborator

Yep, appreciate the heads-up!

@markerikson
Copy link
Collaborator

So, this is bizarre. I just started seeing this myself, in both my local repo and in CI.

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

No branches or pull requests

2 participants