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
Hey @ampersarnie, yeah I'm seeing these on both the 1.1.1 and the pre-release bigbite/build-tools#1.2.0-beta.4 version of the build tools, the unresolved path errors are only seen when using the ?url param though 👍
The text was updated successfully, but these errors were encountered:
ampersarnie
changed the title
Hey @ampersarnie, yeah I'm seeing these on both the 1.1.1 and the pre-release bigbite/build-tools#1.2.0-beta.4 version of the build tools, the unresolved path errors are only seen when using the ?url param though 👍
Unresolved path errors when using the ?url param for images
Mar 20, 2023
Is this still valid after we changed the way SVGs should be imported in #45 ?
Edit: it is still valid. That PR introduced the ability to add ?url to the end of SVG imports and it looks like eslint may report this as a false positive import-js/eslint-plugin-import#1739
Originally posted by @chrishbite in https://github.com/bigbite/content-query/pull/44#discussion_r1142040463
The text was updated successfully, but these errors were encountered: