* chore: add missing fields to package.json
* feat: add postlight org scope to package name
* feat: automate npm publish
* test: npm publish without filters
* fix: add docker image
* test: change directory
* test: add working directory
* fix: defaults syntax
* test: add workspace
* fix: attach workspace
* fix: use standard mercury email
* fix: use ISO time format and preserve original timezone offset
* fix: do not match time zone offset
* chore: move babel runtime-corejs2 to prod deps
* chore: uncomment config to deploy on git tag
* feat: publish to npm public
* adding browser-request
It doesn't seem to impact the build, but technically it should be there
so for good measure, why not...
* chore: roll version back to original state
* feat: add npm-run-all and fix test:web script
* fix: remove test script extra option
* fix: update lint script revert test script and remove npm-run-all
* chore: revert to linux/mac specific script
* fix: prepend node command so it works on windows
* chore: update .nvmrc
* added prettier and pre-commit hooks
* update docker image to new node
* add karma-cli to get web tests working
* explictly install karma... seems to fix problem
* remove pre-built phantomjs
* swap install order
The goal here is to provide some sort of relatively easy preview for the
PR reviewer to see if the fixture looks good, if the parsing is working,
and to make suggestions easily.
Big undertaking to support Mercury in the browser. Builds are working and all tests are passing both for web and node builds. Most code is closely shared.
This commit also swaps in yarn for npm and tweaks circle ci a bit.
* appveyor.yml first go
* changing node
* ps
* narrow it down
* trying this
* fix airbnb module
* trying with yarn
* logging
* hybrid?
* trying yarn w/circle
* bump workers?
* build off?
* updating script
* tweaking script for appveyor
* bumping maxworkers
* cleaning up
* build step?
* yarn it
* added appveyor badge
