mike-eason / oledb Goto Github PK

I think dependents should be able to update or even downgrade edge-js on their own schedule, so they can keep it in sync with their project's Node version.

• the version used can be updated faster or slower than the one used by oledb, which can be locked in via devDependencies
• with "peerDependencies": { "edge-js": "*" }
  • running npm update on dependent projects will do major version bumps of edge-js
  • the latest version can be automatically installed on fresh installs (at least on npm > 7)

To clarify, this isn't a breaking change because no edge-js updates are automatically done after installing the new release with the peer dependency.

What do you think?

Also tried 12.18.0. Had to go all the way back to 10.16.3 to get it working. Any plans to support later versions of node?

I'm trying to use this oledb package from an Electron 6.0.x application that uses Node.js v12.4.0.
The test code, based on the package sample, is:

  const oledb = require('oledb');
  const connectionString = 'Provider=SQLOLEDB;Data Source=(local)\\SQLEXPRESS;Initial Catalog=test;Persist Security Info=True;User Instance=False;User ID=sa;Password=1234;';
  const command = 'select * from TestTable;';
  const db = oledb.oledbConnection(connectionString);
  db.query(command)
  .then(result => {
    console.log(result);
  },
  err => {
    console.error(err);
  });

When starting the Electron application, the following error occurs:

Is there a way I can use electron-edge-js instead edge-js package? electron-edge-js is built against the node.js versions distributed along with Electron releases.