Micha Hanselmann
Micha Hanselmann
@yellow1234 can you please try if this repros on the current version?
IMO this is intended behavior on Windows. If you save a file with type `All Files`, that extension can be anything. The effect becomes even more obvious when you enable...
I'm unable to reproduce this one. Can you try that on a different machine since it sounds suspiciously like a local env issue. Please also try a repro in https://www.electronjs.org/fiddle...
maybe related: https://github.com/nodejs/node/issues/3284 https://github.com/nodejs/node/commit/2d3560767e6da62ceb0e5189c8f0b9a8f0a0924d
@chris-zen haha good one, thanks, appreciate it 😅 - i eventually ditched the Core* stuff and moved on to greener pastures
Ok it's a broader problem, not only configupdater - when I remove that pkg from the buildtarget, it gives me the same error for the next package in the list.
No problems on Ubuntu, this seems to be macOS specific.