internal: Refactor to nimbus

[williaster]

🏠 Internal

This PR is a WIP for moving build configuration to nimbus, which is a soon-to-be open-sourced shareable build config for jest, babel, eslint, prettier, and typescript. This will help

• eliminate duplicate configs across individual packages
• move config to the root for consistency and easier upgrades
• enable easier support for typescript in the future 😉

I will enumerate the changes as the PR evolves below, will try and convert a package at a time, I think the first couple were the hardest.

Changes (dev)

• Use babel not rollup
• Use yarn not npm
  • this will enable workspaces so that we can push all config to the root instead of duplicating across every package as is the case now
• Stricter linting rules (e.g., .jsx required for React files)

Changes (consumers)

• [breaking] Deprecate build/ and dist/, use lib/ and esm/
• [breaking] Deprecate umd builds

General TODO

• point to open-source libs when published
• update docs
• verify all package changes functionally with demo

Packages to convert

• root
• vx-annotation
• vx-axis
• vx-bounds
• vx-brush
• vx-curve
• vx-event
• vx-gradient
• vx-heatmap
• vx-marker
• vx-pattern
• vx-scale
• vx-text
• vx-voronoi
• vx-chord
• vx-demo
• vx-geo
• vx-tooltip
• vx-group
• vx-boxplot
• vx-drag
• vx-clip-path
• vx-network
• vx-legend
• vx-glyph
• vx-stats
• vx-responsive
• vx-threshold
• vx-shape
• vx-point
• vx-mock-data
• vx-hierarchy
• vx-grid
• vx-zoom
• vx-vx

@hshoff @milesj @schillerk @techniq @kristw

[milesj]

NPM/Yarn doesn't use them when installing packages. They are meant for developers/contributors or the project though.

[williaster]

right, Jordan mentioned once that having them can hide bugs/problems in development because developers will be locked into specific versions which consumers might not have on a fresh install.

[williaster]

also upgraded to next@9 because it wasn't transpiling certain react syntax (e.g., <></>) anymore. may have been an invalid .babelrc format for babel@7.

now broke the babel build 🙉

[williaster]

@hshoff @milesj I think this is ready to go if you think the travis.yml and package.json changes look good 🚀 The rest is a lot of linting and file name changes.

We should test out some alpha releases before doing another patch bump. Because of the breaking changes we could also consider a 0.1.0 release 🤔

[williaster]

@hshoff any thoughts on the license compliance fail? it looks like it's flagging next, not sure if that's an issue if it's for the demo package?

[milesj]

The demos are failing on Travis, but its not failing the build. Class properties only available when using next or TS.

[williaster]

enabled next and fixed merge conflicts.