question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

NPM wrong version of ts-essentials being called in

See original GitHub issue

Are you submitting a bug report or a feature request?

bug report

What is the current behavior?

If I install the newest version via npm, my build job breaks because I get.

node_modules/ts-essentials/dist/types.d.ts:5:13 - error TS2322: Type 'K' is not assignable to type 'string'.
  Type 'string | number' is not assignable to type 'string'.
    Type 'number' is not assignable to type 'string'.

5     [key in K]: T;

What is the expected behavior?

Build job succeeds

What’s your environment?

react-final-form: 6.3.0 typescript:3.5.3

Other information

I was able to track it down to what seems like the dependency version that is in NPM for ts-essentials is 2.0.8 but your master branch in this repo is 3.0.2.

I had my package.json install from github instead of NPM and that worked.

The screenshot shows that the installed package has latest version of react-final-form but an old version of ts-essentials

Screen Shot 2019-08-20 at 2 23 14 PM

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:10 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
erikrascommented, Nov 20, 2019

I’m super curious if this project is really being maintained anymore. 7 days to update a simple dependency. =( So sad.

@lookfirst, the sole maintainer has a full time job, a family, and, in August, was writing a brand new, responsive, docs website for this project, and in September and October was speaking at conferences to promote the project. Sorry to sadden you.

1reaction
kgregorycommented, Nov 21, 2019

@erikras I appreciate your efforts and have only a slight idea of what a thankless job it must be at times. Thank you for your work.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to solve npm install error “npm ERR! code 1”
To do this, simply copy the whole dependencies section and devDependencies section from package.json and paste it into a text editor as a...
Read more >
Common NPM Mistakes Every Developer Should Avoid
So, in this article, I will discuss seven common mistakes you should avoid when using NPM. 1. Manually adding dependencies to package.json. You ......
Read more >
Common errors
If you see ENOENT lstat , ENOENT chmod , ENOTEMPTY unlink , or something similar in your log output, try updating npm to...
Read more >
Introducing Volta - it manages your Node.js versions so ...
Ensuring every developer on the team is developing with the correct versions all the time is even harder. But it's essential. While the ......
Read more >
A Comprehensive Guide to Fixing Node-Gyp Issues on Windows
Still getting an installation error? Try installing an older version of Node. If you're on an experimental version, try going back to the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found