FYI, it looks like the maintainers of node-addon-api have released a new version (1.7.1) that should fix the problem on our side. I'll be testing it right after the architecture meeting.
Cheers, Javi On Tue, Jul 23, 2019 at 7:44 PM Javier Hernandez <[email protected]> wrote: > Two hours ago I was creating a new Windows VM to get some work done and to > my surprise, npm install was not working anymore. > > If you try, you'll get an error similar to this one: > https://pastebin.com/0Ghe33Xz > > After investigating the problem, looks like ref-napi (which is a > dependency of ffi-napi) depends on node-addon-api, which an hour ago > received an update which is causing this build failure on our side. > > The maintainers of ref-napi are already aware of it since they have a bot > that takes care of keeping track of changes in its dependencies ( > https://github.com/node-ffi-napi/ref-napi/issues/10#issuecomment-514264471 > ) > > As a workaround, we can add [email protected] to our dependency list > so ref-napi will be happy with such version and won't pull 1.7.0 (the > offending one). I haven't tested this from gpii-app, but I guess that the > same workaround should work. > > I'll keep an eye on this and see if they manage to deal with the situation > shortly. If not, I'll submit a PR tomorrow that allow us to keep going > until the problem is fixed upstream. > > Cheers, > Javi > > >
_______________________________________________ Architecture mailing list [email protected] https://lists.gpii.net/mailman/listinfo/architecture
