3 ms·
> I’m running my project with ts 3.6. Library upgraded to 3.7 and adds null chaining operators. Now my package is broken. Isn't this similar to not upgrading n
by nitsky 6y ago
> I’m running my project with ts 3.6. Library upgraded to 3.7 and adds null chaining operators. Now my package is broken.
Isn't this similar to not upgrading node and using an updated version of an npm package that calls a new function added to the standard library? All npm packages have a minimum node version, and similarly all deno code has a minimum deno version. Both use lockfiles to ensure your dependencies don't update unexpectedly.
> Or, I’m using strictNullChecks. Dependent package isn’t.
This definitely sounds like a potential problem. Because Deno enables all strict checks by default, hopefully library authors will refrain from disabling them.
- jakear 6y agoNode updates much less frequently than TS, so even if it was a problem before, it’s more of a problem now.
- recursive 6y agoNot sure about that. https://nodejs.org/en/download/releases/ https://nodejs.org/en/download/releases/
- jakear 6y agoRephrase: people use new TS features much more often than they use new Node features.
- recursive 6y agoThat might be true in general, but I seem to run into problems with the two with about equal frequency. One of the recent ones I ran into with node was stable array sort.
- nitsky 6y agoYes, npm package maintainers spend a lot of time on node version compatibility. Here is a quote from prettier on their recent v2 release: > The main focus should be dropping support for unsupported Node.js versions. https://github.com/prettier/prettier/issues/6888 https://github.com/prettier/prettier/issues/6888