avoid name clashes

[DerThorsten]

No description provided.

[martinRenou]

Should we port those changes to mambajs's copy of dynload ?

[DerThorsten]

@martinRenou I think we have to. But its not a good situation that we have to maintain two implementations

[DerThorsten]

ignoring the doc workflow build errors atm

[martinRenou]

Agreed it's not a good solution. I'm thinking we should rename mambajs but not sure of a good name yet, what it really is is a package to handle conda packages in the front-end and load them (including load shared libs). How about we rely on mambajs in pyjs?

[DerThorsten]

Agreed it's not a good solution. I'm thinking we should rename mambajs but not sure of a good name yet, what it really is is a package to handle conda packages in the front-end and load them (including load shared libs). How about we rely on mambajs in pyjs?

jeah we should to that. It will just be a bit complicated to integrate it in the build system properly.
So far its pure cmake

[martinRenou]

Something like esbuild could help, without going through the webpack nonsense, with a small script we could build a JS bundle and include it in pre-js.

[DerThorsten]

Something like esbuild could help, without going through the webpack nonsense, with a small script we could build a JS bundle and include it in pre-js.

that would be perfect!