embarklabs
/
embark
mirror of https://github.com/embarklabs/embark.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
6,291 Commits 171 Branches 184 Tags 104 MiB
Commit Graph

64 Commits

Author SHA1 Message Date
dependabot-preview[bot] d0f4236aff build(deps): bump core-js from 3.3.4 to 3.3.5 
Bumps [core-js](https://github.com/zloirock/core-js) from 3.3.4 to 3.3.5.
- [Release notes](https://github.com/zloirock/core-js/releases)
- [Changelog](https://github.com/zloirock/core-js/blob/master/CHANGELOG.md)
- [Commits](https://github.com/zloirock/core-js/compare/v3.3.4...v3.3.5)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
 2019-11-01 12:21:12 -05:00
Michael Bradley, Jr 85235f88b2 chore(release): 5.0.0-alpha.0 2019-10-28 16:05:13 -05:00
Michael Bradley, Jr 1225cb14e8 build(deps): add core-js@3 as a dep to all pkgs that have @babel/runtime-corejs3 dep 
When making use of the `useBuiltIns: 'usage'` option for @babel/preset-env
(which is the case for all transpiled packages in Embark's monorepo) a package
needs to have both @babel/runtime-corejs3 and core-js@3 specified as
dependencies.
 2019-10-28 11:40:48 -05:00
Michael Bradley d17fe33339 build: update babel and webpack dependencies (#1987) 
Includes a switch from core-js@2 to core-js@3
 2019-10-24 17:41:28 -04:00
Michael Bradley ed02cc849f build: bump all packages' engines settings (#1985) 
BREAKING CHANGE:

node: >=10.17.0 <12.0.0
npm: >=6.11.3
yarn: >=1.19.1

node v10.17.0 is the latest in the 10.x series and is still in the Active LTS
lifecycle. Embark is still not compatible with node's 12.x and 13.x
series (because of some dependencies), otherwise it would probably make sense
to bump our minimum supported node version all the way to the most recent 12.x
release.

npm v6.11.3 is the version that's bundled with node v10.17.0.

yarn v1.19.1 is the most recent version as of the time node v10.17.0 was
released.
 2019-10-24 09:52:05 -04:00
Pascal Precht 7881e6a3ac test(@embark/communication): fix failing test (#1979) 
In d6bf5c24b9 we've ensured that certain modules of
embark only executed if their functionality is actually enabled.
This broke one of our tests in the communication module.
This commit fixes the test by explicitly enabling the module's functionality.
 2019-10-21 13:23:43 -04:00
Jonathan Rainville d6bf5c24b9 fix: do not start modules if they are disabled 2019-10-04 10:12:16 -04:00
Pascal Precht 7ea9aa417d test(@embark/commmunication): add test for artifact generation 
This also makes `fakeEmbark` configurable
 2019-10-02 17:40:44 +02:00
Michael Bradley, Jr 17ccd5c1bd build: tidy up the monorepo in prep for v5.0.0-alpha.0 2019-10-01 13:29:53 -05:00
Michael Bradley, Jr 3b649fa455 build: phase 1 of introducing embark-collective 2019-10-01 13:28:13 -05:00
Michael Bradley, Jr 1ba9e4b0a2 test(@embark/communication): remove test stub 2019-09-24 10:14:32 -05:00
Pascal Precht 633683e12f test(@embark/communication): add test for embark communication module (#1908) 2019-09-24 09:44:57 -04:00
Michael Bradley, Jr ba671b9953 test: refactor some recent jest-tests' configuration, placement, and related babel configuration 2019-09-13 19:31:38 -05:00
Pascal Precht e282ae4974 refactor(@embark/communication): move module into own package (#1899) 2019-09-12 17:30:46 -04:00