mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
a69ba4904d
Should fix #10595. Code from the application `node_modules` directory becomes part of the `modules` package, so that it can be imported by any other package that uses the module system, regardless of package load order. Now that we compile code from `node_modules` using `babel-compiler` and `meteor-babel` (#10585), `node_modules` code requires the same runtime environment as any other Meteor JS code. For the most part, this need is satisfied by the `@babel/runtime/helpers/...` modules, which are also defined in the `modules` package because they come from `node_modules`. However, in the legacy bundle, `meteorBabelHelpers.sanitizeForInObject` is used to fix buggy for-in iteration in older Internet Explorers. Thankfully, this extra helper code does not need to be included in the modern or server bundles, but only in legacy code.
5 lines
260 B
JavaScript
5 lines
260 B
JavaScript
// The meteor-babel/plugins/sanitize-for-in-objects plugin generates code
|
|
// that uses meteorBabelHelpers.sanitizeForInObject, but only when
|
|
// compiling code for the web.browser.legacy bundle. See #10595.
|
|
meteorBabelHelpers = require("meteor-babel-helpers");
|