Error: Couldn't find intersection #904

jsg2021 · 2018-09-24T16:10:50Z

Describe the bug

After updating to 0.5, I started getting these errors...

Stack Trace

./node_modules/regenerator-runtime/runtime-module.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error: Couldn't find intersection



  Error: Child compilation failed:
  Module build failed (from ./node_modules/babel-loader/lib/index.js):
  Error: Couldn't find intersection
  
  - ancestry.js:153 NodePath.getDeepestCommonAncestorFrom
    [app]/[@babel]/traverse/lib/path/ancestry.js:153:11
  
  - index.js:244 getSegmentedSubPaths
    [app]/[babel-plugin-minify-builtins]/lib/index.js:244:14
  
  - index.js:92 BuiltInReplacer.replace
    [app]/[babel-plugin-minify-builtins]/lib/index.js:92:31
  
  - index.js:205 PluginPass.exit
    [app]/[babel-plugin-minify-builtins]/lib/index.js:205:27
  
  - visitors.js:193 newFn
    [app]/[@babel]/traverse/lib/visitors.js:193:21
  
  - context.js:53 NodePath._call
    [app]/[@babel]/traverse/lib/path/context.js:53:20
  
  - context.js:40 NodePath.call
    [app]/[@babel]/traverse/lib/path/context.js:40:17
  
  - context.js:97 NodePath.visit
    [app]/[@babel]/traverse/lib/path/context.js:97:8
  
  - context.js:118 TraversalContext.visitQueue
    [app]/[@babel]/traverse/lib/context.js:118:16
  
  - context.js:90 TraversalContext.visitSingle
    [app]/[@babel]/traverse/lib/context.js:90:19
  
  - context.js:146 TraversalContext.visit
    [app]/[@babel]/traverse/lib/context.js:146:19
  
  - index.js:94 Function.traverse.node
    [app]/[@babel]/traverse/lib/index.js:94:17
  
  - index.js:76 traverse
    [app]/[@babel]/traverse/lib/index.js:76:12
  
  - index.js:88 transformFile
    [app]/[@babel]/core/lib/transformation/index.js:88:29
  
  - index.js:45 runSync
    [app]/[@babel]/core/lib/transformation/index.js:45:3

Configuration

babel-minify preset in babel config

babel-minify version: 0.5.0

babel version : 7.1.0

babel-minify-config:

loader: require.resolve('babel-loader'),
options: {
	babelrc: false,
	sourceType: 'unambiguous',
	compact: PROD,
	presets: [
		require.resolve('./babel.config.js'),
		[require.resolve('babel-preset-minify'), {
			mangle: false,
			deadcode: false,
			// simplify: false,
			evaluate: false,
		}]
	]
}

babelrc:

{
    sourceType: 'unambiguous',
    compact: false,
    presets: [
        ['@babel/preset-env', {
            shippedProposals: true,
            targets: [
                '> 1% in US',
                'last 2 versions',
                'not dead',
            ]
        }],
        '@babel/preset-flow',
        '@babel/preset-react',
    ],
    plugins: [
        '@babel/plugin-transform-runtime',
        ['@babel/plugin-proposal-decorators', { legacy: true }],
        ['@babel/plugin-proposal-class-properties', { loose: true }],
        '@babel/plugin-proposal-export-default-from',
        '@babel/plugin-proposal-export-namespace-from',
        '@babel/plugin-syntax-dynamic-import'
    ]
}

The text was updated successfully, but these errors were encountered:

wavded · 2018-09-24T16:12:18Z

Same

ZempTime · 2018-09-25T04:55:58Z

I'm also getting a pretty much identical stack trace when I updated to

"babel-preset-minify": "^0.5.0-alpha.9",

driesd · 2018-09-25T10:39:28Z

I'm also getting the same stack trace with "babel-preset-minify": "^0.5.0-alpha.9".

goozler · 2018-09-25T14:33:39Z

I have the same versions of libs and I had the same issue. Disabling builtIns helped me. I have these options now:

['minify', {
  builtIns: false,
  evaluate: false,
  mangle: false,
}],

It's like a temporary fix

pkuczynski · 2018-09-29T11:18:56Z

Have the same problem. For me it crashes when optimizing following file:

const hasValue = value => Boolean(value) || value === 0

export default hasValue

See babel/minify#904 (comment)

babel/minify#904

wende60 · 2018-10-18T07:46:05Z

confirm that @goozler solution works also for me with the same problems... it works setting only builtIns to false

Example here https://github.com/wende60/Javascript-Gallery

derwaldgeist · 2018-10-26T16:54:53Z

Same here. I tried to upgrade to Babel 7 because of #556, and now the error journey just continues... Pretty disappointing experience.

williaster · 2018-11-12T19:16:03Z

Same error

linorabolini · 2018-11-13T17:35:15Z

Same issue, downgraded to 0.3.0 and it works okay now.

"babel-preset-minify": "^0.3.0",

crespo5 · 2018-11-14T09:42:42Z

Same issue... any solution? For me not works in CLI and in babel preset.

kasperpeulen · 2018-11-16T11:32:17Z

I downgraded to ^0.4.3 to get it working.

CloudPower97 · 2018-12-05T00:12:27Z

I'm experiencing this problem as well... Any solutions?

…inify#904

termitek12 · 2018-12-25T02:46:24Z

For me this is a problem when I minify multiple files or some files that are > 1MB.

If I minify files one by one - everything is ok.

However minify files one by one is annoying and this should be fixed ASAP.

FelixButzbach · 2019-01-16T19:26:18Z

I just switched from babel-preset-babili to babel-preset-minify and I am experiencing the same problem. @goozler s solution worked for me.

danielfazlijevic · 2019-01-20T02:28:37Z

I am experiencing the same problem right now, what's weird is that it works on my PC locally, but when I deploy it to Heroku it crashes

2019-01-20T02:21:49.246316+00:00 app[web.1]:     at NodePath.getDeepestCommonAncestorFrom (/app/node_modules/@babel/traverse/lib/path/ancestry.js:153:11)
2019-01-20T02:21:49.246318+00:00 app[web.1]:     at getSegmentedSubPaths (/app/node_modules/babel-plugin-minify-builtins/lib/index.js:244:14)
2019-01-20T02:21:49.246319+00:00 app[web.1]:     at BuiltInReplacer.replace (/app/node_modules/babel-plugin-minify-builtins/lib/index.js:92:31)
2019-01-20T02:21:49.246321+00:00 app[web.1]:     at PluginPass.exit (/app/node_modules/babel-plugin-minify-builtins/lib/index.js:205:27)
2019-01-20T02:21:49.246322+00:00 app[web.1]:     at newFn (/app/node_modules/@babel/traverse/lib/visitors.js:193:21)
2019-01-20T02:21:49.246323+00:00 app[web.1]:     at NodePath._call (/app/node_modules/@babel/traverse/lib/path/context.js:53:20)
2019-01-20T02:21:49.246325+00:00 app[web.1]:     at NodePath.call (/app/node_modules/@babel/traverse/lib/path/context.js:40:17)
2019-01-20T02:21:49.246326+00:00 app[web.1]:     at NodePath.visit (/app/node_modules/@babel/traverse/lib/path/context.js:97:8)
2019-01-20T02:21:49.246327+00:00 app[web.1]:     at TraversalContext.visitQueue (/app/node_modules/@babel/traverse/lib/context.js:118:16)
2019-01-20T02:21:49.246329+00:00 app[web.1]:     at TraversalContext.visitSingle (/app/node_modules/@babel/traverse/lib/context.js:90:19)
2019-01-20T02:21:49.261822+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2019-01-20T02:21:49.262262+00:00 app[web.1]: npm ERR! errno 1
2019-01-20T02:21:49.263298+00:00 app[web.1]: npm ERR! fonis@0.0.1 start: `set NODE_ENV=production && babel lib/js --out-dir public/js && node ./bin/www`
2019-01-20T02:21:49.263458+00:00 app[web.1]: npm ERR! Exit status 1```

finom · 2019-02-11T21:05:16Z

I tried to use babel-plugin-minify-builtins without any other plugins but still get the same bug.

william-bratches · 2019-02-17T21:09:38Z

Same issue here.

fatlard1993 · 2019-02-19T02:24:57Z

Same issue here. Changing 'minify' to ['minify', { builtIns: false }] as @goozler suggested worked for me for now.

aprilmintacpineda · 2019-03-19T11:08:52Z

In my case this happens intermittently (I'm not sure when) but I've never experienced this when building locally. However, building using runners on GitLab, this happens frequently (about 50 to 60 percent of the time).

dtvn · 2019-07-24T14:12:46Z

For me this is a problem when I minify multiple files or some files that are > 1MB.

If I minify files one by one - everything is ok.

However minify files one by one is annoying and this should be fixed ASAP.

I got a same problem today too.

"babel-preset-minify": "0.5.0"

MichaelOrtho · 2019-09-16T13:20:32Z

In my case it throws this if I use Math.floor. If I change it to Math.round or some other, it passes.

TheDudeFromCI · 2019-11-01T18:59:20Z

I've found this error to be thrown when using Math.max. Commenting that line out allows it to solve.

rfossella · 2020-04-07T04:47:39Z

Oddly, while the 'builtIns': false did work, it did not help me when using babel minify in NPM. I'm actually not even sure how to put that override in the CLI - e.g. npm run build.

But, when I found the offending js program, and compiled/minified that separately it did work.

So, I ended up with a package.json file with min and non-min build commands (where c.js was causing intersection issue)

"scripts": {
    "build": "babel ./a.js ./b.js ./c.js --out-dir ./build",
    "build-min": "babel ./a.js ./b.js --presets minify --out-dir ./build &&  babel ./c.js --presets minify --out-dir ./public/build"}

Singtah · 2020-05-12T21:12:50Z

I am experiencing the same problem right now, what's weird is that it works on my PC locally, but when I deploy it to Heroku it crashes

2019-01-20T02:21:49.246316+00:00 app[web.1]:     at NodePath.getDeepestCommonAncestorFrom (/app/node_modules/@babel/traverse/lib/path/ancestry.js:153:11)
2019-01-20T02:21:49.246318+00:00 app[web.1]:     at getSegmentedSubPaths (/app/node_modules/babel-plugin-minify-builtins/lib/index.js:244:14)
2019-01-20T02:21:49.246319+00:00 app[web.1]:     at BuiltInReplacer.replace (/app/node_modules/babel-plugin-minify-builtins/lib/index.js:92:31)
2019-01-20T02:21:49.246321+00:00 app[web.1]:     at PluginPass.exit (/app/node_modules/babel-plugin-minify-builtins/lib/index.js:205:27)
2019-01-20T02:21:49.246322+00:00 app[web.1]:     at newFn (/app/node_modules/@babel/traverse/lib/visitors.js:193:21)
2019-01-20T02:21:49.246323+00:00 app[web.1]:     at NodePath._call (/app/node_modules/@babel/traverse/lib/path/context.js:53:20)
2019-01-20T02:21:49.246325+00:00 app[web.1]:     at NodePath.call (/app/node_modules/@babel/traverse/lib/path/context.js:40:17)
2019-01-20T02:21:49.246326+00:00 app[web.1]:     at NodePath.visit (/app/node_modules/@babel/traverse/lib/path/context.js:97:8)
2019-01-20T02:21:49.246327+00:00 app[web.1]:     at TraversalContext.visitQueue (/app/node_modules/@babel/traverse/lib/context.js:118:16)
2019-01-20T02:21:49.246329+00:00 app[web.1]:     at TraversalContext.visitSingle (/app/node_modules/@babel/traverse/lib/context.js:90:19)
2019-01-20T02:21:49.261822+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2019-01-20T02:21:49.262262+00:00 app[web.1]: npm ERR! errno 1
2019-01-20T02:21:49.263298+00:00 app[web.1]: npm ERR! fonis@0.0.1 start: `set NODE_ENV=production && babel lib/js --out-dir public/js && node ./bin/www`
2019-01-20T02:21:49.263458+00:00 app[web.1]: npm ERR! Exit status 1```

Same issue here, ok locally but not on Heroku. Would appriciate to know how you fixed it ?

rfossella · 2020-05-13T04:11:45Z

Hi.
As stated in the post, when I did the minify it displayed which file was causing the issue. I tried to minify ONLY that program and it worked. So I created two separate compiles - 1 for the offending program and another for all the others.

"build-min": "babel ./a.js ./b.js --presets minify --out-dir ./build && babel ./c.js --presets minify --out-dir ./public/build"}

[Old timer issue](babel/minify#904 (comment)).

dogia · 2020-07-17T10:51:18Z

Take care if you are using Math.

let movX = Math.abs(currentPosX - this.path[0].posX); let movY = Math.abs(currentPosY - this.path[0].posY);

I was solve my issue changing Math.abs

`let movX = currentPosX - this.path[0].posX;
let movY = currentPosY - this.path[0].posY;

if(movX < 0) movX = (-1) * movX;
if(movY < 0) movY = (-1) * movY;`

Mitsunee · 2020-12-01T14:59:20Z

just happend across this problem with Math.floor() in my little library project. I currently have 2 js files, both of which have the same method convert() in their classes, which uses Math.floor() a bunch. Building these files standalone (see package.json) works fine, but if I try npx babel src -d builds it suddenly gets the same error as op.

Here's the link to the commit where I pushed my current configs: https://github.com/Mitsunee/fox-timers/commit/5a57968d9209a5a34f04952e9954359ab9e80b40

And a screenshot of the error as I'm getting it:

sivaraj-v · 2021-03-30T12:26:48Z

Any update ?

rndm2 · 2021-10-27T12:29:52Z

Still reproduced for me with multiple webpack configurations

joshuambg · 2021-11-14T00:44:30Z

Still an issue for me.

"@babel/core": "^7.4.3",
"babel-minify": "^0.5.1",
"babel-preset-minify": "^0.5.1",
"webpack": "^5.62.1",

Solved with

 "presets": [["minify", { "builtIns": false }]],

…tarea.js` like babel/minify#904

…a.js` like babel/minify#904

ElPrudi · 2022-08-04T16:27:08Z

Yes, still an issue for me.
Had to use

 "presets": [["minify", { "builtIns": false, "mangle": false }]]

esauvisky · 2023-02-28T13:40:58Z

Still an issue. For me, it happens because of String.fromCharCode(). Setting builtIns to false solves it.

jkufrin · 2023-04-27T14:41:34Z

Yes, still an issue for me. Had to use
 "presets": [["minify", { "builtIns": false, "mangle": false }]]

Thanks! That worked for me. And for those using gulp-babel-minify:

.pipe(minify({ "builtIns": false, "mangle": false }))

Error: - Starting 'jsCompile'... 'jsCompile' errored after 341 ms Error in plugin "gulp-babel" Message: /Applications/MAMP/htdocs/calendar/src/js/pages/_pages-calendar-1.js: Couldn't find intersection Solution: - Update the `babel` configuration in the `jsCompile` gulp function. Call the `babel-preset-minify` package with the name `minify` instead and disable the `builtIns` and `mangle` options. Reason: - The reason behind this change may be the use of a newer version of Babel or a related library. The syntax `babel-preset-minify` has been replaced by simply `minify with additional options to customize the behavior of the minification process. The `"builtIns": false` and `"mangle": false` options are disabled in the Babel configuration to prevent the transformation of new native JavaScript methods and objects and to keep variable and property names non-obfuscated, respectively. References: - babel/minify#904 (comment) - https://www.npmjs.com/package/babel-preset-minify

xhemals · 2024-03-30T00:04:15Z

Still had this issue, workaround I had for still being able to have minified code in my build was this:

Setup different environments in babel.config.json

{
  "env": {
    "dev": {
       "presets": [["minify", { "builtIns": false}]]
     },
    "build": {
      "presets": ["minify"]
    }
  }
}

In package.json, declare BABEL_ENV=dev at the start of my npm run dev. And BABEL_ENV=build at the start of my nom run build command.

Hope this helps anyone still having this issue in 2024!

hopolivier · 2024-05-15T18:24:53Z

Hello,
In case someone would like to run babel-minify from the command line, with builtins minifying deactivated, I tried :

babel-minify <filename or directory> --out-dir <output directory> --builtIns false

and it worked for me.

boopathi added the bug Confirmed bug label Sep 25, 2018

vigneshshanmugam mentioned this issue Sep 27, 2018

these code crashes node #909

Closed

driesd mentioned this issue Sep 28, 2018

Bugfix: avoid using Math.max() teamleadercrm/ui#379

Closed

Hypnosphi added a commit to storybookjs/storybook that referenced this issue Oct 2, 2018

babel/minify: use builtIns: false

a4e0e20

See babel/minify#904 (comment)

Hypnosphi mentioned this issue Oct 2, 2018

babel/minify: use builtIns: false storybookjs/storybook#4262

Merged

loganfsmyth mentioned this issue Oct 3, 2018

Couldn't find intersection babel/gulp-babel#166

Closed

fusionstrings added a commit to comeon-group/babel-preset-comeon that referenced this issue Oct 3, 2018

remove babel minify

d660960

babel/minify#904

swernerx added a commit to sebastian-software/babel-preset-edge that referenced this issue Dec 20, 2018

Disable builtIn compression as this throws for some code e.g. babel/m…

7ad597a

…inify#904

kristw mentioned this issue Feb 8, 2019

Set babel-minify builtIn=false williaster/build-config#16

Merged

finom mentioned this issue Feb 11, 2019

Site is not working? circlecell/jscompress.com#40

Closed

Teisi added a commit to Teisi/typo3-gulp-scss that referenced this issue Feb 25, 2019

added workaround for failing js compression: babel/minify#904

f7335cc

ctorgalson mentioned this issue Feb 26, 2020

JS compilation error causes silent failure to compile unrelated components fourkitchens/emulsify-gulp#117

Open

wilsonge mentioned this issue May 28, 2020

[4.0] Update node dependencies joomla/joomla-cms#29253

Merged

slevy85 mentioned this issue Jul 2, 2020

Feat(drawText): add justify text functionnality geongeorge/Canvas-Txt#19

Merged

aralroca mentioned this issue Jul 5, 2020

Implement pagination aralroca/aralroca.com#64

Merged

meduzen added a commit to Sunappu-Dojo/burokku that referenced this issue Jul 5, 2020

Downgrade babel-preset-minify from 0.5 to 0.4.3

798e002

[Old timer issue](babel/minify#904 (comment)).

shilman mentioned this issue Apr 6, 2021

Incompatibility with storybook@6.1.21 whitespace-se/storybook-addon-html#45

Closed

seojihwan mentioned this issue Aug 8, 2021

minify 플러그인 옵션 및 오류 수정 woowacourse-teams/2021-drop-the-code#274

Merged

ehoogeveen-medweb mentioned this issue May 3, 2022

[Bug]: @babel/traverse v7.17.10 broken this scope with dead code elimination plugin #1028

Open

1 task

fritx added a commit to fritx/vue-at that referenced this issue Jul 26, 2022

fix Can't find intersection while try to import `../dist/vue-at-tex…

b4456db

…tarea.js` like babel/minify#904

fritx added a commit to fritx/vue-at that referenced this issue Jul 26, 2022

fix Can't find intersection while importing `../dist/vue-at-textare…

27e99b8

…a.js` like babel/minify#904

toddbaert mentioned this issue Nov 5, 2022

feat: flagd-web provider open-feature/js-sdk-contrib#142

Merged

fritx mentioned this issue Nov 11, 2022

Library update fritx/vue-at#138

Merged

alextselegidis added a commit to alextselegidis/easyappointments that referenced this issue May 3, 2023

Workaround for babel script issues (babel/minify#904)

b47fe90

Error: Couldn't find intersection #904

Error: Couldn't find intersection #904

Comments

jsg2021 commented Sep 24, 2018

wavded commented Sep 24, 2018

ZempTime commented Sep 25, 2018

driesd commented Sep 25, 2018

goozler commented Sep 25, 2018 • edited

pkuczynski commented Sep 29, 2018

wende60 commented Oct 18, 2018 • edited

derwaldgeist commented Oct 26, 2018

williaster commented Nov 12, 2018

linorabolini commented Nov 13, 2018

crespo5 commented Nov 14, 2018

kasperpeulen commented Nov 16, 2018

CloudPower97 commented Dec 5, 2018

termitek12 commented Dec 25, 2018

FelixButzbach commented Jan 16, 2019

danielfazlijevic commented Jan 20, 2019

finom commented Feb 11, 2019

william-bratches commented Feb 17, 2019

fatlard1993 commented Feb 19, 2019

aprilmintacpineda commented Mar 19, 2019

dtvn commented Jul 24, 2019 • edited

MichaelOrtho commented Sep 16, 2019

TheDudeFromCI commented Nov 1, 2019

rfossella commented Apr 7, 2020 • edited

Singtah commented May 12, 2020

rfossella commented May 13, 2020 • edited

dogia commented Jul 17, 2020

Mitsunee commented Dec 1, 2020

sivaraj-v commented Mar 30, 2021

rndm2 commented Oct 27, 2021

joshuambg commented Nov 14, 2021

ElPrudi commented Aug 4, 2022 • edited

esauvisky commented Feb 28, 2023

jkufrin commented Apr 27, 2023

xhemals commented Mar 30, 2024

hopolivier commented May 15, 2024

goozler commented Sep 25, 2018 •

edited

wende60 commented Oct 18, 2018 •

edited

dtvn commented Jul 24, 2019 •

edited

rfossella commented Apr 7, 2020 •

edited

rfossella commented May 13, 2020 •

edited

ElPrudi commented Aug 4, 2022 •

edited