oslllo / svg-fixer

Converts SVG Strokes To Fill.
https://docs-oslllo-com.onrender.com/svg-fixer/master
MIT License
213 stars 19 forks source link

GLib-GIO-WARNING #60

Closed pongells closed 2 years ago

pongells commented 2 years ago

Hello,

when I run the library via node (I have not tested via CLI) I get this warning:

(process:16016): GLib-GIO-WARNING **: 18:37:43.785: Unexpectedly, UWP app `microsoft.windowscommunicationsapps_16005.11629.20316.0_x64__8wekyb3d8bbwe' (AUMId `microsoft.win
dowscommunicationsapps_8wekyb3d8bbwe!microsoft.windowslive.mail') supports 1 extensions but has no verbs

It seems to be working anyway, but the warning itself is annoying. Any way this can be fixed or silenced?

Thanks

Ghustavh97 commented 2 years ago

Hi, thanks for the issue.

  1. What are the reproduction steps / code snippet of hoe the package is being called.
  2. What is your environment e.g OS, node version etc....
pongells commented 2 years ago

Hello,

the warning appears when I require the library:

const svgFixer = require('oslllo-svg-fixer');

I am on Windows, and using ts-node to run my CLI script (written in typescript), the tsconfig.json is:

{
  "compilerOptions": {
    "target": "es6",
    "module": "commonjs",
    "esModuleInterop": true,
    "resolveJsonModule": true,
    "strict": true,
    "lib": [
      "es2019"
    ],
    "types": [
      "node"
    ]
  },
  "include": [
    "src"
  ],
  "exclude": [
    "**/*.spec.ts"
  ]
}

node version is 14.16.0 :)

Ghustavh97 commented 2 years ago

I think this might be caused by they way microsoft outlook was installed on you system, check this out https://stackoverflow.com/questions/67607643/what-does-this-warning-mean-it-happens-every-time-i-restart-the-node-process

I also failed to reproduce it on my side

Capturewwwww

Captureww

pongells commented 2 years ago

weird.. well it's a minor inconvenience, I'll try to dig a bit more into it when I get some time. thanks for the feedback :)

Ghustavh97 commented 2 years ago

no problem, let me know if you find a fix for it and feel free to reopen the issue if the problem is really coming from this package.