intentionally malformed package.json fixture in tests breaks flowtype when checking node_modules
See original GitHub issueSteps to regenerate:-
npm install resolve
- run
flow
command
flow output:-
Error ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ node_modules/resolve/test/resolver/malformed_package_json/package.json:2:1 Unexpected end of input, expected the token }
1│ {
2│
@ljharb, Kindly respond. Thank you
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Flow type checker errors in node_modules/* - Stack Overflow
I'd advise against doing this. If an NPM package has first class Flow support, this will cause flow to ignore its typings. –...
Read more >eslint | Yarn - Package Manager
An AST-based pattern checker for JavaScript. ast, lint, javascript, ecmascript. readme. npm version Downloads Build Status FOSSA Status
Read more >How to Remove Flow Issues in Node Modules? | by BlueEast
Open .flowconfig file and write the below stated code. [ignore].*/node_modules/*[include][libs] ...
Read more >pact-js
But I?m getting the following Pact test errors: ``` console.error node_modules/@pact-foundation/pact/pact.js:110 Pact verification failed! console.error ...
Read more >Apache Traffic Control Documentation
vice are {test} and a client makes a request for /?test=something they will ... as a whole or to Traffic Ops itself, whereas...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://github.com/facebook/flow/issues/2364
Hi @ljharb ,
I have ignored the lib in flow config. Previously ignoring lib isn’t working, but now it is.