Stop shipping 'fixture/broken/' to npm

[ryan953]

We need to ignore these files. Test files don't really need to be installed by package consumers, and by default projects with flow enabled will trip up over the broken files in here. It's not a great experience.

[3rd-Eden]

Why not fix flow?

…

On May 19, 2017, 7:29 PM -0400, Ryan Albrecht ***@***.***>, wrote: We need to ignore these files. Test files don't really need to be installed by package consumers, and by default projects with flow enabled will trip up over the broken files in here. It's not a great experience. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub (#5), or mute the thread (https://github.com/notifications/unsubscribe-auth/AABtp-9Oc-gDiySEqFp61cpRASOSfrO5ks5r7iXjgaJpZM4NhHKq).

[ryan953]

We could definitely suggest something to flow directly. I'm not sure what to ask of them though.

In this case you have an invalid json file (invalid on purpose) that ends up in the node_modules folder.
It makes sense that they find the json files in node_modules, because those files have structure and types. They can be imported into any JS module. So inspecting files and preserving g types makes sense in that case.

So you have a better suggestion, I'll take it over there