babel/packages
Stanislav Sysoev 33da726638 Not null check in babel-helper-builder-binary-assignment-operator-visitor (#3647)
Fix: T7537 — https://phabricator.babeljs.io/T7537

When transforming super call in class constructor, part of ast is replaced using method "replaceWithMultiple" here:
https://github.com/babel/babel/blob/master/packages/babel-plugin-transform-es2015-classes/src/vanilla.js#L379

It leads to removing the node (replacing it with null) here:
https://github.com/babel/babel/blob/master/packages/babel-traverse/src/path/replacement.js#L51

But parent ExpressionsStatement is still untouched and when it reaches visitor generated in here
https://github.com/babel/babel/blob/master/packages/babel-helper-builder-binary-assignment-operator-visitor/src/index.js#L18

It blows up because expression is null from previous visitors.
2016-08-31 14:41:49 -04:00
..
2016-02-12 11:29:58 -05:00
2016-08-24 17:40:46 -06:00
2016-06-26 20:21:26 -04:00
2016-08-24 17:40:46 -06:00
2016-08-24 17:40:46 -06:00
2016-05-02 19:43:49 -04:00
2016-05-17 14:49:17 -04:00
2016-05-02 19:43:49 -04:00
2016-05-17 14:49:17 -04:00
2016-05-02 19:43:49 -04:00
2016-05-17 14:49:17 -04:00
2016-05-02 19:43:49 -04:00
2016-05-02 19:43:49 -04:00
2016-05-02 19:43:49 -04:00
2016-05-02 19:43:49 -04:00
2016-05-17 14:49:17 -04:00
2016-08-24 17:40:46 -06:00
2016-05-02 19:43:49 -04:00
2016-05-02 19:43:49 -04:00
2016-05-02 19:43:49 -04:00
2016-08-04 19:34:51 -04:00
2016-08-04 19:34:51 -04:00
2016-08-04 19:34:51 -04:00
2016-08-04 19:34:51 -04:00
2016-08-04 19:34:51 -04:00
2016-08-04 19:34:51 -04:00
2016-05-02 19:43:49 -04:00
2016-05-02 19:43:49 -04:00
2016-05-02 19:43:49 -04:00
2016-08-04 19:34:51 -04:00
2016-08-24 17:40:46 -06:00
2016-07-12 22:33:58 -04:00
2016-08-24 17:40:46 -06:00
2016-08-24 17:40:46 -06:00
2016-06-27 17:19:48 -04:00
2016-02-06 19:06:41 -05:00
2016-08-04 19:34:51 -04:00
2016-08-04 19:34:51 -04:00
2016-06-26 20:21:26 -04:00
2016-08-24 17:40:46 -06:00
2016-07-26 18:12:25 -04:00
2016-08-24 17:40:46 -06:00
2015-10-29 17:51:24 +00:00

Woah, what's going on here?

A monorepo, muhahahahahaha. See the monorepo design doc for reasoning.