Tracking issue: NPM publishing

[turbocrime]

• typescript version and @typescript-eslint/typescript-estree incompatible #718
• Add changeset support (npm publishing part 1) #672
• Wildcard exports #750
• stop using barrel files #724
• Publish crypto-web package to npm #893
• Publish storage package to NPM #892
• Proving keys should be handled by the package that uses them #676
• rename @penumbra-zone/router package + publish to npm #684
• Publish wasm package to npm #737
• Publish transport-chrome package to npm #894
• eliminate @penumbra-zone/constants #733
• target esnext #741
• disaggregate @penumbra-zone/services-context package into HandlerContext #730
• Publish UI package to npm #738
• disaggregate @penumbra-zone/query package #731
• ui package exports are complex #728
• Improve external deps import paths #736
• Mocks should use actual interfaces #680
• Convert from CJS to ESM #749
• Dropping the /src/  #762

[turbocrime]

#722 may be relevant if we don't bundle when publishing.

currently tsconfigs all extend a parent config in another package. this won't be included in pack, so tsconfig in the package will just break

[TalDerei]

are there remaining issues in this tracking issue that are outdated and not relevant anymore?

[TalDerei]

closing as complete