Skip to content
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

fibers@3.1.1 not compatible with Node 12? #178

Closed
rsinger86 opened this issue Jun 4, 2019 · 4 comments
Closed

fibers@3.1.1 not compatible with Node 12? #178

rsinger86 opened this issue Jun 4, 2019 · 4 comments

Comments

@rsinger86
Copy link

Thanks for this amazingly useful tool - I really love the API.

I can't get flightplan to work with Node 12 because it appears that flightplan depends on fibers@3.1.1, but that version of fibers is incompatible with Node 12.

Would it be possible to update to version 4 of fibers?

@cullylarson
Copy link

cullylarson commented Jun 4, 2019

I'm having the same problem. Using node 12 on macos, failing to build fibers@3.1.1. Getting errors like this:

> fibers@3.1.1 install /Users/me/npm/lib/node_modules/flightplan/node_modules/fibers
> node build.js || nodejs build.js

  CXX(target) Release/obj.target/fibers/src/fibers.o
../src/fibers.cc:68:2: error: no template named 'Handle'
        Handle<String> NewLatin1String(Isolate* isolate, const char* string) {
        ^
../src/fibers.cc:69:10: error: no viable conversion from returned value of type 'Local<v8::String>'
      to function return type 'int'
  ...String::NewFromOneByte(isolate, (const uint8_t*)string, NewStringType::kNormal).ToLocalChecked();

../src/fibers.cc:72:2: error: no template named 'Handle'
        Handle<String> NewLatin1Symbol(Isolate* isolate, const char* string) {
...

Fibers@4 builds fine, but like @rsinger86 said, flightplan depends on fibers@3.

@pstadler
Copy link
Owner

pstadler commented Jun 6, 2019

Glad you like this project. Please provide a PR.

@Zwimber
Copy link

Zwimber commented Jun 17, 2019

Checked and the commit seems to work!

@pstadler
Copy link
Owner

This has been fixed with 0.6.20. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants