zhirzh/flow-babel-webpack-plugin

Flow typecheck status in Webpack build reports

flow-babel-webpack-plugin's Issues

What license is this code under?

Hi Shirsh! What's the license for this repo?

Unnecessary error log?

Whenever I get a Flow error, the log at the bottom has:

Please wait. Server is garbage collecting shared memory: -Please wait. Server is rechecking (starting up): \Please wait. Server is rechecking (garbage collecting shared memory): |Please wait. Server is rechecking (parsed files 0/1 (0.0%)): /Please wait. Server is rechecking (garbage collecting shared memory): -Please wait. Server is rechecking (resolving dependencies): \Please wait. Server is rechecking (garbage collecting shared memory): |Please wait. Server is rechecking (calculating dependencies): /Please wait. Server is rechecking (merged files 0/6 (0.0%)): -Please wait. Server is rechecking (finishing up): \Please wait. Server is handling a request (starting up): |Please wait. Server is handling a request (collating errors): /

It'd be nice to strip this out so that just the Flow error is reported.

I'm on Flow 0.64.0

Update flow-bin 0.34.0 (or make it a peerdependency)

flow-bin version is out of date for npm version

npm package version is other than here and flow-bin is out of date.

Since author doesn't accept pull requests better use forked version

NPM doesn't have latest fix

The latest commit (68eb459) is not included in the npm package so the error prints twice.

Thanks for this plugin, btw!

node_modules

Is it any way to not show errors from node_modules?

Importance of transform-flow-comments

First, thanks for writing/maintaining this awesome plugin!

Second, I'm wondering if using the transform-flow-comments plugin is absolutely necessary. My preference would be for the types to be stripped by Babel, but if I use transform-flow-comments, the commented types don't get stripped.

My app seems to be working just fine for now without using the additional plugin—Babel strips the type annotations and they don't show up in my source files or in my bundle. Do you expect that I'll run into major issues at some point if I don't use transform-flow-comments, or does it seem safe to go forward without it and re-introduce it if I run into any problems?

Build speed is slow.

After this plugin was applied, build speed was too slow.

Couldn't find type "$Diff"

By some reason, compilation with this plugin fails with error Couldn't find type "$Diff"
I case when flow is ruined manually everything works ok

Show errors in browser

Forgive me for not investigating this myself (on the train when I discovered this), but do the errors propagate to the browser console the way things like ESLint errors do?