There are situations where two packages have the same API, but the implementations are for separate platforms. If you control each package, you could theoretically combine them and use .web.js and .ios.js for every file in the package (and possibly share some modules with common functions). But it may be easier to keep the implementations split between two packages and simply have the bundler determine which package should be used depending on platform (or maybe some other heuristic).
Unsure on what the API would look like for redirection. I'll update this issue at a later date.
There are situations where two packages have the same API, but the implementations are for separate platforms. If you control each package, you could theoretically combine them and use
.web.jsand.ios.jsfor every file in the package (and possibly share some modules with common functions). But it may be easier to keep the implementations split between two packages and simply have the bundler determine which package should be used depending on platform (or maybe some other heuristic).Unsure on what the API would look like for redirection. I'll update this issue at a later date.