-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new faviconPath
option
#312
Conversation
🦋 Changeset detectedLatest commit: 187b820 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
// Use the favicon from the config if specified, otherwise don't use anything | ||
const favicon = playroomConfig.faviconPath | ||
? relativeResolve(playroomConfig.faviconPath) | ||
: undefined; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've defaulted to undefined
here because I believe the /images folder is not published to npm, and I'm not sure if you want to do that. However, I'm happy to change this if needed.
SVG icons aren't supported at all in Safari, and some mobile browsers. I would suggest that it's not worth worse browser support for a slight simplification. This issue can be fixed without also adding a feature too. The feature should be discussed/implemented separately. |
This PR fixes issue #311 (which appears to be breaking builds in version
0.34.1
) by adding a newfaviconPath
option.I've also tried to simplify the favicon implementation by replacing the
favicon.png
andfavicon-inverted.png
files with a single SVG favicon.