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
I'm following with-global-stylesheet example and I'm trying to correctly configure it to use with blueprintjs.com, that include some icon fonts. When the page is loaded on browser, it requests /resources/icons/icons-16.eot, that is handled by Next that doesn't find the fonts, even when I copy that dir on the project root.
I've tried to configure next.config.js' webpack to load the fonts, but considering that this url is requested from a third-party css, it didn't worked.
Another option is to rewrite css url() to point to static folder, but I wasn't able to make it work (I'm a webpack newbie yet).
So, my suggestion it to handle any unknown route as static asset, that could workaround this problem.
The text was updated successfully, but these errors were encountered:
Got this fix from issue #2302. Libraries like `font-awesome` are pretty common. Indicating how to get them to work should be indicated in the `README.md` (if not added to the example)
lockbot
locked as resolved and limited conversation to collaborators
May 11, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm following
with-global-stylesheet
example and I'm trying to correctly configure it to use with blueprintjs.com, that include some icon fonts. When the page is loaded on browser, it requests/resources/icons/icons-16.eot
, that is handled by Next that doesn't find the fonts, even when I copy that dir on the project root.I've tried to configure next.config.js' webpack to load the fonts, but considering that this url is requested from a third-party css, it didn't worked.
Another option is to rewrite css
url()
to point to static folder, but I wasn't able to make it work (I'm a webpack newbie yet).So, my suggestion it to handle any unknown route as static asset, that could workaround this problem.
The text was updated successfully, but these errors were encountered: