Fixed this error when added this package.
While processing files with less (for target web.browser):
packages/accounts-ui/login_buttons.less:1: Unknown import:
{accounts-ui-unstyled}/login_buttons.less
Fixes#4810.
The es5-shim package can be removed by expert users who do not wish to
support older browsers, or who wish to support older browsers using a
different shim library.
To enable that use case, we do not register a strong dependency on the
es5-shim package in the core meteor package, but we do ensure that
es5-shim loads first when it is installed.
The Babel parser is faster, it has to be installed (unlike Esprima, which
can be removed after a few more changes like this), and better matches the
parsing we do for ECMAScript transpilation.
The jscript plugin works around various limitations of older Internet
Explorer versions, in particular those described here:
http://kiro.me/blog/nfe_dilemma.html
This included removing some internal version constraints. It would be
nice if package A could say "use B@2.0.0" (when both have changed), but
when they're both in the release, we need to make a release that has a
B@2.0.0-rc in it, which doesn't match that constraint. Fortunately,
constraints aren't necessary within a release anyway.
- Upgrade to a newer (unreleased) version which supports
function k({} = {}) {}
and doesn't also crash
- Filter out boring warnings
- Don't use ES7 syntax that JSDoc doesn't support in one file that
has JSDoc in it
I thought we could rely on isobuild:compiler-plugin for this, but it's
not good enough: a package could have dependencies that are satisfiable
without choosing a dependency version with a compiler plugin, yet choose
that dependency version at publish time and become ineligble for legacy
builds.
Adds rate limiting to Meteor in the form of a default rule in accounts_rate_limit for user creation, login attempts and password resets. It also adds a DDPRateLimiter that allows users to add rules to methods and subscriptions.
