As a developer, I want to be able to support latest Node.js version (13.x) in order to use the latest engine features and to make sure all internal CLI users will be able to use my applications.
I work on internal business projects that are being used by developers, mostly through local CLI and distant Web interfaces. Some of them are on Node 12, some upgraded on 13 (we kept our servers on Node 12). Currently, the CI fails tests when on Node 13, not able to find the proper binding, which is supposed to be node-v79-linux-x64. However, the binding I get when on Bitbucket pipeline image node:latest is node-v72-linux-x64. All my CI tests are failing on the latest Node.js version because of this, but are successful on Node 12, on which binding resolves to node-v72-linux-x64. I use your package through knex.
Would it be something that you can fix in the next few weeks?
As a developer, I want to be able to support latest Node.js version (13.x) in order to use the latest engine features and to make sure all internal CLI users will be able to use my applications.
I work on internal business projects that are being used by developers, mostly through local CLI and distant Web interfaces. Some of them are on Node 12, some upgraded on 13 (we kept our servers on Node 12). Currently, the CI fails tests when on Node 13, not able to find the proper binding, which is supposed to be
node-v79-linux-x64. However, the binding I get when on Bitbucket pipeline imagenode:latestisnode-v72-linux-x64. All my CI tests are failing on the latest Node.js version because of this, but are successful on Node 12, on which binding resolves tonode-v72-linux-x64. I use your package throughknex.Would it be something that you can fix in the next few weeks?