liamcmitchell/url-io

Read and mutate data using a standard interface

url-io's Issues

createSafeSource doesn't resolve Promises

Because nested promises are automatically resolved when consuming as a promise, this leads to inconsistent values when observing as an observable.

const io  = createIO(() => Promise.resolve(1))
io('/').subscribe((v) => console.log(v)) // Promise
io('/').then((v) => console.log(v)) // 1

Async modules

Hi,

I'm thinking about lazy loading a module so that webpack splits my bundle and the module is loaded on demand, not eagerly.
Something naive like that:

createIO({
  /module': (request) => {
    System.import('module/source').then((handler) => handler(request))
  },
})

Right now, I'm under the impression that only the handlers themselves are asynchronous, but the whole path resolving mechanism does not handle promises at all.

At the moment, the only way I see to handle code splitting is to actually have a very thin IO configuration and all its handler starting with a System.import().
That way, the IO stuff is loaded eagerly (but should be very thin) and the (hopefully) heaviest parts can still be lazy loaded.
However, this is not very efficient as the module has to be written specifically to handle code splitting.

Do I understand correctly? Do you have a better way of approaching code splitting? Does url-io require modification to support that?

Thank you.