Introduce tests & CI

[dy]

This PR introduces a showcase for baseline tests (pilot).
Now CI is available for gl-components (yay).
That should reduce complexity of test coverage for gl-based traces in plotly.

Also that makes gl-component tests look way less messy, in standard tape- fashion.
@etpinard @archmoj please see test.js, hope that will make further dev simpler and fix regressions (seems that palette work may cause some).

[etpinard]

Hmm. You no longer convert es6 -> es5?

[dy]

bubleify does not do async/await bublejs/buble#125, and seems there is no more maintenance.
I wished there was a way for browserify to indicate this transform for main export, but ignore that for running tests.
Probably I should include babelify. Or just simply rewrite the thing in ES5, that is not a lot of hassle. Rollup maybe?

[etpinard]

npm test is working for me locally 🎉

[dy]

@etpinard there is a way to bundle the package as well, without sacrificing the dependencies. That is not as elegant as just browserify with --ignore, but the latter is unfortunately broken for that use-case.

That adds:

• ES5 compilation on prepublish
• tree shaking, if required
• Removes glslify and other browserify runtime transforms (plotly bundling gets faster)
• Keeps shared dependencies instead of packing them to bundle (ignore option)
• Enables target browser versions via browserslist option https://github.com/browserslist/browserslist

[etpinard]

build

[etpinard]

Well, that's annoying. How many more bytes is that going to result in plotly.js? Oh well, maybe plotly.js is already too big to care about bundling glslify twice.

[dy]

@etpinard glslify does not get bundled, that just inlines glsl dependencies to a bundle. Now in plotly.js glslify does inlining whenever we run plotly build, but with that PR glslify is not required anymore, because glsl is inlined already, so plotly building gets faster.

Moreover, right now plotly building also runs bubleify, that performs the same transpilation internally. With that PR we cut that as well, by providing transpiled code.

More to that, with this PR glslify is not a production, but dev dependency, meaning that plotly.js package as a dependency is faster to run with browserify, and the component is quicker to install.

[dy]

@etpinard should we proceed with that?

[etpinard]

Looks like I was completely wrong in #15 (comment), building plotly.js off the latest commit on this branch results in a slightly smaller bundle:

That said, looks like this PR here breaks a bunch of plotly.js tests:

• (plotly.js) $ npm run test-image-gl2d barfs, there are still some non ES5 tokens in the regl-scatter2d bundle.js that don't get along with our old nw.js image test server.
• (plotly.js) $ npm run test-jasmine -- --tags=gl spits out a bunch of

errors.

• (plotly.js) $ npm run test-syntax gives:

[dy]

Oh Lord, I've found that. regl-splom uses wrong regl-scatter2d entry, pointing to not a bundle.
@etpinard can you please check tests with gl-vis/regl-splom#10
They run fine on my side.

[etpinard]

plotly.js tests are green, 💃

Thanks @dy !