v0.8.0 isn't published on npm

[ctataru]

Hello!

I've been trying to use this module for a project of mine, but I'm running into a few issues (#24), which are entirely solved by v.0.8.0.

Is there any way that you could publish the new version on npm?

Thanks :)

[chazzmoney]

Additionally, the 0.7.0 release seems to be unable to read files written by 0.7.0. So publishing this would solve a big bug.

[ctataru]

How are you trying to read the files, @chazzmoney?
I have no issue reading the files in Spark, but attempting to read a file that contains an array, in PrestoDB, is impossible. The same problem exists in v0.8.0, though.

This issue has already been outlined in #30.

[chazzmoney]

With further research, I'm not sure that 0.7.0 is writing files correctly at all. See the issue I opened (#35 ). I can write files, but they don't seem to work anywhere. Upgrading to 0.8.0 manually has fixed both issues for me.

[ericholiveira]

I also cant make 0.7.0 version to work at all... I'm using node-parquet while waiting for the 0.8.0 to be deployed on npm

[dnwarnock]

0.7.0 appears to be missing support for nested types. If you create a schema with a nested type an error is thrown because the type field isn't in the top level of the field definition. This issue appears to be fixed in the latest version of the code. I suggest bumping the version on npm so other can avoid hitting this road bump.