@sam-github @davidcheung Taking over PR to get it landed quicker. Added in comments and reference to issue at mapbox. Review the additional comments please.

LGTM

Is this fixed now? Have been waiting all evening. :-)

New patch version is needed. Hopefully they publish it soon. ⌛️

@HenrikGr @dzonatan Just published it now. 👍

Thank you very much, is just to run npm install -g apiconnect again?

I have uninstalled everything, reinstalled node.js 4.5.0, upgraded NPM to 3.x.x and installed windows-build-tools.

@HenrikGr : Yes, but first remove existing apiconnect, if any (just to have a clean install, IMO), using:
npm uninstall apiconnect -g and then install again.

Hmm, got the same message, checked the npm-debug.log file and it says it tried to install [email protected].
I did delete npm and the npm-cache directory before installing reinstalling node.js and upgraded npm to 3.x.x.

I'm located in Sweden, could that play a part in it? :-)

I asking just becaus I try to learn.

@HenrikGr This is only for slc (npm install -g strongloop), we need to coordinate for apiconnect still, finding out if someone is on it now.

Upgrading strongloop/strongloop to sqlite3@^3.1.6 as we speak at #327

Landed #327, will go out with next release.

God morning. Is it coordinated with apiconnect yet?

Morning, sqlite3 released a [fix to sqlite3@^3.1.6[(https://github.com/mapbox/node-sqlite3/commit/de2055b67196e95379c08b7405c39701559e3c25) which is automatically picked up by apiconnect, meaning it should work for you now.

Thank you for all your help, appreciate it.

I could see it used version 3.1.6 now, but I got an error about to long file names/paths.

It seemed to be related to windows-build-tools. I need to do some further investigation.

@HenrikGr make sure you are using npm@3, it uses shorter paths by default, might clear the issues