Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Don't use path.replaceWith() with a source string, use path.replaceWithSourceString()

See original GitHub issue

ERROR in unknown: Don’t use path.replaceWith() with a source string, use path.replaceWithSourceString()

Seems to be the result of this change : https://github.com/babel/babili/pull/543/files

Issue Analytics

State:
Created 6 years ago
Reactions:5
Comments:31 (8 by maintainers)

Top GitHub Comments

6reactions

Xazzzi-CTcommented, Jun 19, 2017

Is this on npm yet? Asking because i still get this error message.

6reactions

j-f1commented, Jun 16, 2017

@michaeltrim Can you try replacing node_modules/babel-plugin-minify-constant-folding/lib/index.js with this patched version to see if that fixes it?

Top Results From Across the Web

Babel plugin error: Don't use `path.replaceWith()` with a ...

babeljs - Babel plugin error: Don't use `path. replaceWith()` with a source string, use `path. replaceWithSourceString()` - Stack Overflow. ...

[Solved]-Babel plugin error: Don't use `path.replaceWith ...

Coding example for the question Babel plugin error: Don't use `path.replaceWith()` with a source string, use `path.replaceWithSourceString()`-babel.js.

Babel-plugin-handbook - npm.io

When you have a visitor that has a Identifier() method, you're actually visiting the path instead of the node. This way you are...

babel-core API

Scope (path, parentScope); function babel-core.traverse.cheap (node, enter) ... if (typeof replacement === "string") { throw new Error("Don't use `path.

Package Diff: babel-traverse @ 6.5.0-1 .. 6.6.0

"use strict";. @@ -159,15 +160,19 @@. throw new Error("Don't use `path.replaceWith()` with a source string, use `path.replaceWithSourceString()`");. }.