cjs bundle means lodash deps for mocking are pulled in on production apps about time HOT 4 CLOSED

This wouldn't be a problem if we were able to use ES module versions of the packages (rather than bundled cjs)

Why can't you use ES modules?

from time.

If I yarn add @cycle/time, it installs the package compiled down to cjs.

eg. rxjs.js looks like

"use strict";
exports.__esModule = true;
var Observable_1 = require("rxjs/Observable");
require("rxjs/add/observable/from");
var adapt_1 = require("@cycle/run/lib/adapt");
var mock_time_source_1 = require("./dist/mock-time-source");
var time_driver_1 = require("./dist/time-driver");
adapt_1.setAdapt(function (stream) { return Observable_1.Observable.from(stream); });
function mockTimeSource(args) {
    return mock_time_source_1.mockTimeSource(args);
}
exports.mockTimeSource = mockTimeSource;
function timeDriver(_, adapter) {
    return time_driver_1.timeDriver(_, adapter);
}
exports.timeDriver = timeDriver;

Am I missing some yarn or npm command to pull in an ES module version?

(From my experience adding the package from github and trying to use the ts files directly (e.g. using tsloader and webpack) has never seemed to work well - maybe I should pull it in from github then try to compile it from typescript to an es module version before bundling?)

from time.

Ugh, good catch. Can you please open this over on the cyclejs repo, this repo is soon to be closed down? We definitely need to do something about this, and maybe set up a package size benchmark to prevent further unintentional bloat.

from time.

Can do! @Widdershin cyclejs/cyclejs#660

from time.