- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Hugo 0.64 missing files in mounts #6854
Comments
The latest Boostrap 4 SASS source fails to build with Hugo. We can do a bug trade ... |
I think this has already been fixed in master. Is there any issue about this? |
@XhmikosR no issue, and yes it's fixed in master. Also, this issue should be fixed now. Sorry for the breakage; I had to dive into my own code to fix a related issue for 0.64, and I had a hard time understanding my own code, so I more or less rewrote the mount file system. That would have been splendid if we had solid test cases for your situation. I took the Bootstrap site for a spin. Notice you build the SCSS source with Hugo -- pretty nice editing experience, I suspect. |
We actually build only the docs SCSS with Hugo. In master there's no need to install anything else to fiddle with the docs :) |
And thanks for the quick fix! |
A little heads up about my latest addition to master: 40ba7e6 -- which updates LibSass to the newest release version. I tested it with the Bootstrap site and it "looked fine". node-sass is still on some old version (3.5.5?). Nothing particularly new functionality in this LibSass, but they're in the process of porting all the upstream Dart changes for LibSass 4.0 (Sass Modules ...?). |
Yup. We test from time to time with Dart Sass for the core, and I plan to at least build everything on each commit with Dart Sass so that we at least catch compilation errors. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes.
This does not happen with v0.63.2.
The text was updated successfully, but these errors were encountered: