Export parseModule and generateCode in a different module that doesn't rely on node api

[paoloricciuti]

Describe the feature

Currently parseModule and generateCode are exported from the code module that import node:fs this made them impossible to use in a browser environment when actually they are not really dependent on node apis.

Maybe we can consider export them from another module that does not depends on node api to allow their usage even in the browser.

Additional information

• Would you be willing to help implement this feature?

[antfu]

Yeah I think it makes sense to have a submodule for that. PR Welcome :)

[paoloricciuti]

Yeah I think it makes sense to have a submodule for that. PR Welcome :)

Should I still re-export them from the current module to avoid breaking changes?

[antfu]

Yes. I think we could have magicast/browser or magicast/core for that.

[Hugos68]

@antfu Do you want magicast/browser to also re export all other things like types, helpers etc, or have magicast/browser only export parseModule and generateCode. I'm in need of magicast in a browser env. Creating a PR as we speak.