Closed teleclimber closed 2 years ago
It's not clear why we need this functionality in ds-host. If we are developing an improved library, then having it fully sorted out in ds-dev should be enough? If it's close enough to being ready that it's being tested in ds-host, it could be published as a beta?
The sandbox generates a import.json for deno that prevents all local code except white-listed dirs from being loaded as modules.
This is a problem when developing new dropserver_app library version locally, and for dropserver_interfaces too. Would be good to make it feasible to tell ds-dev and ds-host to load alternative versions via import map. This would imply doing something like this in import map:
In ds-host we could just add to the config, but ds-dev doesn't have a config right now, so not as clear.