Issue while using it with Angular 4 about trilogy HOT 6 CLOSED

@citycide
repo :-> https://github.com/vrbagal/Angular-4-Electron-

from trilogy.

@vrbagal it's possible this is actually because of TypeScript but I'll have to look more into it.

from trilogy.

Also, if you have time it'd help a lot if you push up a repo I can pull down to test this out.

from trilogy.

I pushed a fix in e1d57c3 that drops defining module.exports for the .mjs / module build.

Released in v1.2.1

from trilogy.

Could you please add code snip to import and use it with typescript, I am not able to get it running with this repo

from trilogy.

Hmm. Original issue's fixed but it looks like there's a new one ( or two ). I've been trying to track them down but it's pretty easy to get tangled in webpack's webs...

using sql.js

__webpack_require__.i(...) is not a function

I'm not well versed in webpack's innards but this seems like a webpack issue. That API isn't working for some reason. I guess it could be the fact that node's path ( which is what's being replaced by webpack's require above ) isn't an ES module so importing while in an .mjs module could potentially be the issue? 🤷‍♂️

using sqlite3

This one I know more about than the above:

Cannot read property 'create' of undefined

... which I traced through knex into its usage of generic-pool. The problem is that we have this tree:

$ npm ls generic-pool
[email protected] C:\......\Angular-4-Electron-
`-- [email protected]
  +-- [email protected]
  `-- [email protected]
    `-- [email protected]

generic-pool v3.0.0 ( which trilogy itself uses ) had a breaking change to its Pool constructor's signature. For whatever reason webpack is giving knex [email protected] when it should be getting its own [email protected] dependency. That seems pretty jacked to me. We'll probably have to open an upstream issue with webpack.

from trilogy.