-
Notifications
You must be signed in to change notification settings - Fork 335
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
steps to add node support are not working #2967
Comments
Milestone: Someday. Label: #new. What's next? A reviewer should examine this issue. |
I googled on this error and it looks like it is something with the node module fibers not compatible with Node 12. What versions of fibers do you use? |
Not sure. It's something Cappuccino uses internally I guess or maybe something that one of its dependencies uses internally. |
I believe Fibers is installed when you run the file |
It looks like you get fibers version 1.0.15 installed on line 10
|
True. I just spent some more time fiddling with this and independently found |
I don't do development based on Node and Javascript usually (precisely why I'm here: for Objective-J), so after half an hour of playing with it, I still don't know how to work around this PR al6x/synchronize#73 not being merged, or the updated I also think Cappuccino 1.0.0's starter bundle's package.json might be using some outdated syntax for specifying |
To install the branch used in that pull request linked above al6x/synchronize#73, edit
This installs
At this point, running
However, this is beyond what I can reasonably figure out how to fix. In fact, now I'm afraid I may have broken my rhino-based install... |
-#new |
Milestone: Someday. Label: tools. What's next? A reviewer should examine this issue. |
@ivucica did you get it working in the meantime? |
Is this still an issue, with current Node/npm minimum version requirements? |
i do not think so, because nobody else complained so far. |
I have not tried this since. If I try again and it’s still broken for me, I
can just reopen the bug.
On Fri 7 Jan 2022 at 18:35, daboe01 ***@***.***> wrote:
@ivucica <https://github.com/ivucica> did you get it working in the
meantime?
—
Reply to this email directly, view it on GitHub
<#2967 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADUTHDIZMMU4DXB4DRGQMDUU4W5ZANCNFSM4VXDVTZA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Sent from Gmail Mobile
|
+#works-for-me |
Milestone: Someday. Labels: #works-for-me, tools. What's next? Attempts to reproduce the problem described by this issue have failed to reveal any erroneous situation. |
Milestone: Someday. Labels: #works-for-me, tools. What's next? Attempts to reproduce the problem described by this issue have failed to reveal any erroneous situation. |
Just some information if someone reads this in the future. The current Node version is a total rework of the earlier try with a Node engine for Narwhal based on Fibers. This problem is not relevant anymore. Anyone who wants to use the Node version should follow the install instructions on https://github.com/cappuccino/cappuccino/wiki/node |
Trying to follow the steps listed here:
https://www.cappuccino.dev/blog/2017/04/cappuccino-on-node-js.html
The npm-install script fails with several errors, beginning with:
macOS 10.15.7
Xcode 12.2
Node 12.18.4
Cappuccino latest
The text was updated successfully, but these errors were encountered: