Jens Habegger

Reproducible in latest Win10. I took a look at the respective source code and suspect [this __Dirname call](https://github.com/electron/fiddle/blob/b074071333d1fa775dbbfc46e5df3c5fa50ff72c/src/renderer/templates.ts#L19); I remember webpack having similar issues with production Electron applications. However, building...

I took a closer look at the problem. While the dev console itself does not offer any hints on whats happening, [getFile](https://github.com/electron/fiddle/blob/38b7b08691fc0988cdc4416bcaf694b7a1db5e50/src/renderer/templates.ts#L21) in [templates.ts](https://github.com/electron/fiddle/blob/master/src/renderer/templates.ts) catches the following error: ``` "Error:...

I'm surprised this issue hasn't gotten more attention over the years: * These potentially long lists of warnings for missing peer dependencies create a *lot* of noise. * Spamming warnings...

I've taken a closer look at this issue. * Most (if not all) of the development effort is now focused on Yarn2 * Yarn2 handles these warnings a lot better...

Same issue here, attempting to use 0.1.15 of both llama-node and llama-cpp with ggml q5_1 versions of different models, it looks like Llama is not properly initialized. ``` Loading LLamaCpp...

This is probably caused by synchronously calling ```llama.load(config);```. Properly awaiting this async generator solves the problem.

I can confirm this behavior, currently using the following configuration: ``` this.log = bunyan.createLogger({ name: 'log', level: this.lvl, streams: [{ type: 'rotating-file', path: './logs/log.log', period: '1h', count: 24 }] });...