Ville Saukkonen

I played around with this idea today and couldn't find a way to manage NPM tags in scale using Lerna so ended up making an issue of it: https://github.com/lerna/lerna/issues/1936 I'm...

Looks like NPM has builtin support for default tags: https://docs.npmjs.com/files/package.json.html#publishconfig

Hit next problem with Lerna: https://github.com/lerna/lerna/issues/1980 Also Yarn workspaces prevents from having multiple packages with same name. Not sure if yarn workspaces are needed though.

Nothing new unfortunately :/ Haven't had really time to put effort on this. Looks like Lerna (the project) is pretty difficult to setup locally. I should try how it turns...

@retyui yeah something like that! It's possible to push new versions with same version number & tag to NPM. That's how Definitely-typed does it too.

I believe so. Note that the libdefs normally just gets more accurate (closer to reality) over time. If you think this is a problem, you can always rely on committing...

Some updates: @goodmind has done excellent research on the topic and looks like Flow gets mad if there is package.json within libdef files: https://github.com/facebook/flow/issues/7746

I think incomplete typedefs are also better than nothing. But it could be good to communicate it somehow and have guidelines for people to follow: Let's say you have following...

Hi @maxaggedon! Looks like the libdef is failing on 0.85.0. The reason is that 0.85.0 is much stricter with type annotations, see: https://medium.com/flow-type/asking-for-required-annotations-64d4f9c1edf8 Would you be willing to fix those...

@beaucollins I think this is a bit problematic, for the same reasons why native `.values` returns mixed. See e.g https://github.com/facebook/flow/issues/2221#issuecomment-323861218 and https://github.com/facebook/flow/issues/2221#issuecomment-238749128 For exact objects it's a different story though,...