-
-
Notifications
You must be signed in to change notification settings - Fork 80
Latest build broken? ERROR in ./node_modules/graphology/dist/graphology.mjs 2:0-44 #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you provide more details like what build system you are using? |
maybe I'm misunderstanding, but I believe its just create-react-app's default build system |
https://codesandbox.io/s/reagraph-example-forked-8flnt8?file=/src/App.tsx I forked the example sandbox code and updated the package to 4.11.1 and it also got an error.. |
I was able to solve this by specifying the following in
Reference to the thread graphology/graphology#489 (comment) |
The latest build is also breaking for me:
|
Give 4.12.1 a shot please |
i get the same error
…________________________________
From: Austin ***@***.***>
Sent: Monday, August 14, 2023 7:23 AM
To: reaviz/reagraph ***@***.***>
Cc: Tinah Hong ***@***.***>; Comment ***@***.***>
Subject: Re: [reaviz/reagraph] Latest build broken? ERROR in ./node_modules/graphology/dist/graphology.mjs 2:0-44 (Issue #115)
Give 4.12.1 a shot please
—
Reply to this email directly, view it on GitHub<#115 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO325YGKPY47RNMN4ZBT6VLXVIKFZANCNFSM6AAAAAA25VHI7I>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I also got the same error. Node.js 18.16.1
|
i think this should be fixed now. |
@amcdnl I am still getting an error. I think 3 imports need to be fixed:
https://github.com/search?q=repo%3Areaviz%2Freagraph+%22from+%27graphology-%22&type=code |
@hverlin - Could you raise a PR for that? I can merge and release it after. |
@amcdnl I think this should do it: #135 While waiting for this I used the following workaround with a
"pnpm": {
"patchedDependencies": {
"reagraph@4.14.0": "patches/reagraph@4.14.0.patch"
}
}
|
Thanks @amcdnl, I can confirm that the latest version ( |
Thanks for your contribution too @hverlin !! |
Describe the bug
I just installed reagraph in my project - version 4.11.1.. I tried the example in the readme:
And it kills the react client.. lots of errors like this:
The text was updated successfully, but these errors were encountered: