Monorepo structure

[karesztrk]

On my side the Zig build is failing with the following:

/home/ktorok/Projects/md4w/packages/core/build.zig:12:33: error: no field named 'path' in union 'Build.LazyPath'
        .root_source_file = .{ .path = "src/md4w.zig" },
                                ^~~~
/usr/lib/zig/std/Build.zig:2171:22: note: union declared here
pub const LazyPath = union(enum) {
                     ^~~~~
referenced by:
    build: /home/ktorok/Projects/md4w/packages/core/build.zig:4:14
    runBuild__anon_8819: /usr/lib/zig/std/Build.zig:2116:27
    remaining reference traces hidden; use '-freference-trace' to see all reference traces
/home/ktorok/Projects/md4w/packages/core/build.zig:12:33: error: no field named 'path' in union 'Build.LazyPath'
        .root_source_file = .{ .path = "src/md4w.zig" },
                                ^~~~
/usr/lib/zig/std/Build.zig:2171:22: note: union declared here
pub const LazyPath = union(enum) {
                     ^~~~~

[karesztrk]

You may want to extend the README, @ije

[ije]

On my side the Zig build is failing with the following:

please use zig 0.11, the wasm build output of zig 0.12+ is significantly increased. i still wonder what change happened, and i have a plan to rewrite it in pure zig.

[karesztrk]

I see. If you have any other improvement ideas then let me know. By the way, I wished to name the webcomponent part like md4w/webcomponent but that's an invalid name. That would require a scope package. Do you have plans towards scoped packages?

[karesztrk]

@ije are you still considering the merge of our works into a monorepo? If not then we can close this.

[ije]

sorry for the late reply and thanks for your contribution, i feel this PR beyonds the simple goal of being a wasm module wihtout deps. why not keep the md4wc in your scope and put the link in this repo?

[karesztrk]

Sure, no problem