Publish flowtype-protoc-gen on npm

[shanshanzhu]

Suggestion: We can use beta version first for testing.

To Do List

• Agree on proposals for versioning
• Convert to use yarn and yarn.lock
• Remove flow=true config flag, generate flow type by default
• Fix build failure https://travis-ci.org/chrisgervang/flowtype-protoc-gen
• Fix package.json and publish

Any more thoughts?

[chrisgervang]

For now, I don't want to convert to yarn or remove typescript code paths until we've got a stable release out. The original package had a build system in place that used npm, since it works and bazel is set up already - I'd prefer not to change it (instead prioritizing new features).

[shanshanzhu]

Sure. agree with the priority. I move remove typescript specific code path and yarn to other tasks.

For yarn and the build system: it depends on the consumer after it is published on npm.
Example 1: It is used by javascript repo that use yarn for dependency management. Running generate.sh will install dependency in the root node_modules folder that is not tracked in the repo's yarn.lock file. Also javascript repo that use yarn add flowtype-protoc-gen to install this package will install different versions of node_modules from 'package-lock.json' that's in the root repo, but those versions may not be used.

See #8

[chrisgervang]

Maybe I'm not familiar enough with yarn. My understanding was that an npm package published with or without yarn will behave the same for the end user installing over npm because they are installing a "built" distribution of the package.

All of the devDependencies are ignored, and we don't have many dependencies

"@babel/polyfill": "^7.0.0",
"google-protobuf": "^3.6.1"

(the poly fill might actually be able to be removed)
It may make sense to move google-protobuf to peerDependency.

[chrisgervang]

This is now published in prerelease on npm