# Relative asset paths issue in SCSS files - Sage 9

**URL:** https://discourse.roots.io/t/relative-asset-paths-issue-in-scss-files-sage-9/20705
**Category:** sage
**Tags:** webpack, sage9
**Created:** 2021-04-29T20:19:06Z
**Posts:** 9
**Showing post:** 2 of 9

## Post 2 by @strarsis — 2021-04-29T20:28:16Z

You may find the Sage 9.1 update branch interesting as this should fix most if not all build/watch issues:

e class='quote' data-post="1" data-topic="20067"\> 
 ![](https://discourse.roots.io/user_avatar/discourse.roots.io/strarsis/48/4543_2.png)
[Sage "9.1": Please test](https://discourse.roots.io/t/sage-9-1-please-test/20067) [sage](/c/sage/11)

> Note: Changed Sage 9.2 to 9.1 (as 9.0.10 is the current release in master). Updated Sage 9.x You can now try out the Sage PR branch for webpack 5 and updated dependencies. The sage-installer which is used by Sage 9.x for adding framework support was also updated to add the right configuration and styles. Bootstrap 5 (Beta2) has been added for selection. Tailwind 2 is used now. Trying it out now! To prevent siloing of existing working forks of Sage 9 + (insert framework), please try this set…

---

_[View the full topic](https://discourse.roots.io/t/relative-asset-paths-issue-in-scss-files-sage-9/20705)._