feat: provide browser-ready bundle (requires zod import-map)

[brettz9]

No description provided.

[brettz9]

The --legacy-output option seems to be the one way it won't overwrite our existing dist/index.js file (overwriting it may be ok as far as Node, but wouldn't think so for TypeScript which writes to different files).

[Gregoor]

Let's give it a shot!

[brettz9]

Looks like there was a publish error: https://github.com/commonbaseapp/zodex/actions/runs/11071258234/job/30762829124

[brettz9]

The error is indicating you've already published "0.0.0-dev". Is this some kind of bug with semantic-release?

[Gregoor]

Hm yeah maybe, it was working before, it's not clear to me from the log what might have broken

[brettz9]

Shall I file an issue with https://github.com/go-semantic-release/action ?

[Gregoor]

I think we should be able to figure this out, it ran just fine before merging this PR:

So I guess we just need to figure out: what changed OR what isn't deterministic about our CI

[brettz9]

The changes though would need to look back, I think, to the last version (the previous PRs didn't fail as they didn't necessitate a version change), and there have been a number of changes, including the workspace changes, since that version was published: v0.18.2...v0.19.0 .

[Gregoor]

true, you're right, I looked at the wrong thing!

[brettz9]

Don't know how well this applies, but per go-semantic-release/semantic-release#77 , there is no support for monorepos in go-semantic-release.

This comes up as a top Google search result: https://github.com/pmowrer/semantic-release-monorepo and has instructions for pnpm.

[Gregoor]

Uuh yeah dang, that makes a lot of sense, I didn't think about those implications, thank you for doing that for me. I'll do some thinking from here how to resolve it!

[brettz9]

Hiya... Wondering if you might have some time to revisit this?

[Gregoor]

I fear I won't be finding the time for it in the next while, sorry!