mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
0042ae55f1
This split gives us the ability to use different sets of polyfills for server and client, which allows us to take better advantage of native support in Node 4+. We now rely on core-js as a peer dependency on the client (which is a win because core-js is always installed along with babel-runtime), and as an Npm.depends-style dependency on the server (which is necessary because there's not always an an application to provide peer node_modules on the server, e.g. in isopackets and compiler plugins). Since we're using different sets of polyfills on the client and the server, it didn't seem to make sense to rely on a single npm package, so meteor-ecmascript-runtime has been removed.
ecmascript-runtime-server
Source code of released version | Source code of development version
Polyfills for new ECMAScript 2015 APIs like Map and Set