error node_modules/react-native-vector-icons/lib/create-icon-set.js: #<WeakSet> could not be cloned. #1334

superchaoran · 2021-04-12T06:31:12Z

error node_modules/react-native-vector-icons/lib/create-icon-set.js: #<WeakSet> could not be cloned.
Error: #<WeakSet> could not be cloned.
    at Object.serialize (node:v8:260:7)
    at _default (node_modules/@babel/core/lib/transformation/util/clone-deep.js:16:30)
    at normalizeFile (node_modules/@babel/core/lib/transformation/normalize-file.js:52:36)
    at normalizeFile.next (<anonymous>)
    at run node_modules/@babel/core/lib/transformation/index.js:31:50)
    at run.next (<anonymous>)
    at /node_modules/@babel/core/lib/transform-ast.js:20:41
    at Generator.next (<anonymous>)
    at evaluateSync (/node_modules/gensync/index.js:251:28)

using "react-native": "0.64.0", and "react-native-vector-icons": "^8.1.0"

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

Rananjaya · 2021-04-23T13:26:26Z

same here

QasimJaffry · 2021-04-24T18:48:18Z

any solution to this? I'm facing this error too

Hamashassan · 2021-04-25T23:41:25Z

same issue any solution?

Hamashassan · 2021-04-25T23:42:04Z

many libraries are throwing this issue

Error: # could not be cloned.

codynguyen · 2021-04-28T13:03:00Z

Same here, I just upgraded rn from 0.61.5 to 0.64 and got this issue

setharell · 2021-04-28T17:43:29Z

has anyone found a solution to this problem?

Silver-IT · 2021-04-28T21:46:12Z

Me too. I got this error. How can we solve this?

error: node_modules\react-native-vector-icons\lib\create-icon-set.js: # could not be cloned.

Silver-IT · 2021-04-29T23:47:35Z

I have tried with these versions and finally I can build it.

...
"react-native": "0.63.0",
"react-native-vector-icons": "^6.6.0",
...

But I don't think it is working properly. Too slow or sometimes stuck.

Hope this works fine.

japhet247 · 2021-05-03T08:38:42Z

Facing the same issue
RNN ~> 0.64.0
vector-icons ~> ^8.1.0

japhet247 · 2021-05-03T09:22:02Z

I think the problem might be with @babel/core and @babel/runtime versions. I downgraded to the below versions and it worked for me;

"@babel/core": "^7.12.9",
"@babel/runtime": "^7.12.5",

Silver-IT · 2021-05-03T09:48:56Z

@japhet247 , Do you mean with "react-native 0.64.0" and "react-native-vector-icons 8.1.0" ?

japhet247 · 2021-05-04T10:40:19Z

@Silver-IT , Yes

jmikulka · 2021-05-04T22:21:59Z

As @japhet247 said, downgrading @babel/core and @babel/runtime versions fixes the problem.

If you keep using the versions from the React Native template (https://github.com/facebook/react-native/blob/0.64-stable/template/package.json#L17), you will get higher versions of these libraries (see you package-lock.json):

"@babel/core": "7.14.0",
"@babel/runtime": "7.14.0",

To fix the problem, only allow patch version updates:

"@babel/core": "~7.12.9",
"@babel/runtime": "~7.12.5",

This will install:

"@babel/core": "7.12.17",
"@babel/runtime": "7.12.18",

Hope that helps.

oblador · 2021-05-06T06:26:31Z

Hi, i'm unable to reproduce this with a fresh 0.64 project, most likely this is a problem with your babel setup like @jmikulka mentions. Try setting it to

    "@babel/core": "^7.14.0",
    "@babel/runtime": "^7.14.0",

thainquet · 2021-05-24T08:58:48Z

As @japhet247 said, downgrading @babel/core and @babel/runtime versions fixes the problem.

If you keep using the versions from the React Native template (https://github.com/facebook/react-native/blob/0.64-stable/template/package.json#L17), you will get higher versions of these libraries (see you package-lock.json):
"@babel/core": "7.14.0",
"@babel/runtime": "7.14.0",
To fix the problem, only allow patch version updates:
"@babel/core": "~7.12.9",
"@babel/runtime": "~7.12.5",
This will install:
"@babel/core": "7.12.17",
"@babel/runtime": "7.12.18",
Hope that helps.

I got this working in react-native 0.64.1 and react-native-vector-icons 8.1.0

But in my case, i need to upgrade @babel/core and @babel/runtime to the lastest version:

yarn upgrade --dev @babel/core
and yarn upgrade --dev @babel/runtime

later, check package version to be sure that i installed with the lastest version
yarn list --pattern @babel/core => └─ @babel/core@7.14.3
yarn list --pattern @babel/runtime => └─ @babel/runtime@7.14.0

After that, i clean xcode builds then rebuild again and everything works like a charm!

githubdoramon · 2021-06-11T13:07:01Z

"@babel/core": "7.12.17",
"@babel/runtime": "7.12.18",

Thank you SO MUCH

tylers-username · 2021-06-16T08:08:06Z

For those of you dealing with hours of debugging @babel/core being installed at multiple versions, here's the savior—add this to your package.json

  "resolutions": {
    "@babel/core": "7.12.*",
    "@babel/runtime": "7.12.*"
  },

mjylfz · 2021-07-20T06:18:50Z

Parameters of async methods cannot have default values. If the default value is taken, this error will be reported. The root cause is not clear for the time being. You can modify the source code through patch.

This will solve the problem

Mathie01 · 2021-08-31T20:49:43Z

Same problem
I lowered the versions of babel but same problem

@mjylfz I can't find the code of your screenshot in my node_modules ?

cristianoccazinsp · 2021-09-02T21:50:32Z

I don't think this is even related to this library, but I've been having the same issue with babel ever since trying to upgrade to RN 0.65.1

Any other work arounds?

raimonkh · 2021-09-06T18:29:58Z

Same issue with another library, downgrading metro doesn't seem to work.
For RN 65 the minimum required versions are higher than the ones we are trying to resolve to...

ezranbayantemur · 2021-09-08T08:47:52Z

I've tried babel upgrading but it didn't worked. All that bug occured after another lib update (which is not connected to vector-icons) and don't know why or how.

Like (and thanks to) @mjylfz said you should change the default value setting on async function on source code.

On <project-root>/node_modules/react-native-vector-icons/lib/create-icon-set.js file; change all the async functions (which are loadFont and getImageSource) default parameter setting.

As like;

...
...
  async function getImageSource(
    name,
    size,
    color
  ) {
    size = size || DEFAULT_ICON_SIZE,
    color = size || DEFAULT_ICON_COLOR
...
...
  async function loadFont(file) {
    file = file || fontFile
...
...

raimonkh · 2021-09-08T09:04:32Z

What worked for us in the end was not related to babel.
we recreated yarn.lock and Podfile.lock and it all worked well after cleaning all node modules and caches... likely some old dependency hanging around.
If stuck, try deleting those files and recreatim them (cleaning the caches). I know many people do this regulary but we don't. So likely the problem will go away that way

dan-lee · 2021-09-09T13:22:35Z

For those of you dealing with hours of debugging @babel/core being installed at multiple versions, here's the savior—add this to your package.json
  "resolutions": {
    "@babel/core": "7.12.*",
    "@babel/runtime": "7.12.*"
  },

Unfortunately this doesn't seem to work with react-native@0.65.1 anymore:

Unknown option: .browserslistConfigFile.

And if I patch that out, I get:

Cannot find module '@babel/plugin-transform-react-jsx'

I feel like this is a rabbit hole I don't want to go down

cristianoccazinsp · 2021-09-09T13:32:41Z

What worked for me was the same. Delete the lock files and all your node modules. Re-install everything, and double check your lock file to ensure only one babel dependency is listed.

raimonkh · 2021-09-09T13:51:43Z

I second deleting the lock files, it also worked for me

dan-lee · 2021-09-09T14:20:21Z

Thanks, @cristianoccazinsp, and @raimonkh for your suggestion! There was actually an older version lying around which I wasn't aware of 🙌

jplandry908 · 2021-09-13T21:38:15Z

FYI - Deleting the lock files worked for me as well

Vannevelj · 2021-10-04T11:06:23Z

The resolutions solution still worked for me, going from 0.64.0 to 0.65.1

eliot1019 · 2021-10-19T04:20:41Z

@Vannevelj you were able to stay on the babel 7.12 versions but not see the Unknown option: .browserslistConfigFile. error when running react-native bundle?

eliot1019 · 2021-10-20T18:27:12Z

We ended up getting around this issue by staying on babel 7.12 using resolutions but grepping for browserlistConfigFile and patching metro to just delete the lines that have that option. We were going from RN64.2 -> RN65.1

blackbing · 2021-10-21T03:28:04Z

@eliot1019 what do you mean "patching metro to just delete the lines that have that option" ?

hussainarthuna · 2021-11-09T12:11:50Z

Facing the Same issue with "react-native": "^0.66.1" and "react-native-vector-icons": "^9.0.0"
Any help will be appreciated.
Thank you.

mifi · 2021-11-18T05:09:32Z

I just did a yarn upgrade and then pod install in the project and that did the trick for me! (of course with the side-effect that all dependencies got upgraded according to their semver in package.json)

Works even with "@babel/core": "^7.13.8" and "@babel/runtime": "^7.13.8" in package.json.

So I'm guessing some dependency or sub-dependency had this bug that got solved after upgrading it to the latest patch/minor

TheRusskiy · 2021-11-24T21:54:31Z

Removing yarn.lock is a nuclear solution, thankfully there's a better way.
Go to yarn.lock, see where "@babel/*** start and delete all of them, dependencies are in alphabetical order, so it's easy selecting them.
The next time you do yarn install it's going to re-generate only babel dependencies which should solve this problem.

douglasjunior · 2021-12-02T21:31:18Z

Parameters of async methods cannot have default values. If the default value is taken, this error will be reported. The root cause is not clear for the time being. You can modify the source code through patch.

This will solve the problem

How did this work in previous versions of React Native without issues?

e-monson · 2021-12-09T21:58:45Z

I hate babel so much. The absolute worst problems I encounter in JS development always boil down to some cryptic babel issue that NO ONE understands. I'd rather still write ES5 than deal with problems like this.

phuongwd · 2022-01-11T14:24:47Z

Thanks @TheRusskiy #1334 (comment)

Removing yarn.lock is a nuclear solution, thankfully there's a better way. Go to yarn.lock, see where "@babel/*** start and delete all of them, dependencies are in alphabetical order, so it's easy selecting them. The next time you do yarn install it's going to re-generate only babel dependencies which should solve this problem.

and it also working on this version

"@babel/core": "^7.16.7",
"@babel/runtime": "^7.16.7",

siderakis mentioned this issue May 3, 2021

I have an error when make debug build. (error node_modules/react-native-keyboard-aware-scroll-view/lib/KeyboardAwareHOC.js: #<WeakSet> could not be cloned.) anyone have this error facebook/react-native#31413

Closed

oblador mentioned this issue May 6, 2021

node_modules/react-native-vector-icons/lib/create-icon-set.js: #<WeakSet> could not be cloned. #1332

Closed

2 tasks

Mathie01 mentioned this issue Sep 10, 2021

#<WeakSet> could not be cloned. rnmapbox/maps#1523

Closed

macfanatic mentioned this issue Nov 2, 2021

Yarn on 0.65 throws a heap out of memory error facebook/react-native#32027

Closed

FelixMo42 mentioned this issue Nov 12, 2021

Metro suddenly started to fail in React Native Application facebook/metro#652

Closed

johnf closed this as completed Aug 3, 2023

error node_modules/react-native-vector-icons/lib/create-icon-set.js: #<WeakSet> could not be cloned. #1334

error node_modules/react-native-vector-icons/lib/create-icon-set.js: #<WeakSet> could not be cloned. #1334

Comments

superchaoran commented Apr 12, 2021

Rananjaya commented Apr 23, 2021

QasimJaffry commented Apr 24, 2021

Hamashassan commented Apr 25, 2021

Hamashassan commented Apr 25, 2021

codynguyen commented Apr 28, 2021

setharell commented Apr 28, 2021

Silver-IT commented Apr 28, 2021

Silver-IT commented Apr 29, 2021 • edited Loading

japhet247 commented May 3, 2021

japhet247 commented May 3, 2021

Silver-IT commented May 3, 2021

japhet247 commented May 4, 2021

jmikulka commented May 4, 2021 • edited Loading

oblador commented May 6, 2021

thainquet commented May 24, 2021 • edited Loading

githubdoramon commented Jun 11, 2021

tylers-username commented Jun 16, 2021

mjylfz commented Jul 20, 2021 • edited Loading

Mathie01 commented Aug 31, 2021

cristianoccazinsp commented Sep 2, 2021

raimonkh commented Sep 6, 2021

ezranbayantemur commented Sep 8, 2021

raimonkh commented Sep 8, 2021

dan-lee commented Sep 9, 2021

cristianoccazinsp commented Sep 9, 2021

raimonkh commented Sep 9, 2021

dan-lee commented Sep 9, 2021

jplandry908 commented Sep 13, 2021

Vannevelj commented Oct 4, 2021

eliot1019 commented Oct 19, 2021 • edited Loading

eliot1019 commented Oct 20, 2021

blackbing commented Oct 21, 2021

hussainarthuna commented Nov 9, 2021

mifi commented Nov 18, 2021 • edited Loading

TheRusskiy commented Nov 24, 2021

douglasjunior commented Dec 2, 2021 • edited Loading

e-monson commented Dec 9, 2021

phuongwd commented Jan 11, 2022

Silver-IT commented Apr 29, 2021 •

edited

Loading

jmikulka commented May 4, 2021 •

edited

Loading

thainquet commented May 24, 2021 •

edited

Loading

mjylfz commented Jul 20, 2021 •

edited

Loading

eliot1019 commented Oct 19, 2021 •

edited

Loading

mifi commented Nov 18, 2021 •

edited

Loading

douglasjunior commented Dec 2, 2021 •

edited

Loading