You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I created this PR I noticed that when I tried to open another link it was asking me if I approve this new Chrome on my system.
🤔But, I didn't install a new Chrome... Okay lets "Show Application"
😑Usually I would run new apps in isolation with npm install --ignore-scripts and/or in a container, but being so trusting of svelte, and in order to pass the svelte tests I did not use the safer approach.
I don't know if anything could or should be done about it but I'm sharing the story as an issue for the community to see and discuss.
Thanks for your time, -TC
The text was updated successfully, but these errors were encountered:
Some of Svelte's tests (the custom element ones, where jsdom wouldn't cut it) use Puppeteer, which uses Chromium under the hood. I haven't heard other reports of this behavior (and don't use macOS myself), but presumably this is something you should ask Puppeteer about. We're not doing anything weird or asking them to register Chromium as your default browser.
After I created this PR I noticed that when I tried to open another link it was asking me if I approve this new Chrome on my system.
🤔But, I didn't install a new Chrome... Okay lets "Show Application"
😑Usually I would run new apps in isolation with
npm install --ignore-scripts
and/or in a container, but being so trusting of svelte, and in order to pass the svelte tests I did not use the safer approach.I don't know if anything could or should be done about it but I'm sharing the story as an issue for the community to see and discuss.
Thanks for your time, -TC
The text was updated successfully, but these errors were encountered: