fix: Use node package.json as template for pkg/package.json

[kylebarron]

No description provided.

[github-actions]

Asset	Size	Compressed Size
report_pkg/async_full/parquet_wasm_bg.wasm	6.7MB	1.3MB
report_pkg/slim/parquet_wasm_bg.wasm	4.9MB	678KB
report_pkg/sync/parquet_wasm_bg.wasm	6.2MB	1.2MB

[amoeba]

Hey @kylebarron, I ran into this and I can confirm the fix in this PR would work for me. I have a local ESM project and was able to get import { readParquet } from "parquet-wasm/node"; working once I added this post-install script to delete the type field from the package.json:

-- >8 -- 
  "scripts": {
    "postinstall": "node -e \"const fs=require('fs'),p=JSON.parse(fs.readFileSync('./node_modules/parquet-wasm/package.json'));delete p.type;fs.writeFileSync('./node_modules/parquet-wasm/package.json',JSON.stringify(p,null,2));\"",
-- >8 -- 

[kylebarron]

Thanks for the acknowledgement. I think we might need a wholesale re-architecting of how the builds are made, along with good dev docs about how it works

[amoeba]

Do you want to file an issue and put your thoughts down? And if you don't think you'd have time to do it, I can try.

[kylebarron]

I don't have the time/energy to put into this project right now 😕

Happy to follow your suggestions to unblock some of these recurrent issues