-
SummaryI set up a project yesterday and ran into some warnings on install and errors on build. I'm wondering if I should create an issue or if this is something that should be handled here in the discussions. The main issue here is The warnings and errors are shown in the steps to reproduce below. I'm thinking that the warnings about some functions that will stop working in the next major version and so on, is more for the developers to help update the templates with up to date functions and dependencies, but please correct me on that if I'm wrong. In addition to the issues mentioned below, I also stumbled upon #1360 and downgraded Hugo to v0.145.0 which at least fixed that issue, but the main issue remains. More details
When I first tried this, I thought the build process still created a After some more troubleshooting and internet searching, I didn't get anywhere, so today I figured I'll just try and see if this is reproducible and post something here. It turns out it is reproducible, but it still might be a local issue in my environment, so I'll post some specs and steps below. SpecsSteps to reproduceGenerates a bunch of warnings. Generates some of the previous warnings. Generates some of the previous warnings again. Generates some of the previous warnings and the main error message. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
Thanks for reporting your findings — I will take them into account! I'm working on updating Doks for the latest Hugo (with high priority, available soon) — see also thuliteio/create-thulite#47 |
Beta Was this translation helpful? Give feedback.
-
This is the new way: https://purgecss.com/getting-started.html And this is what the new template should look like/now looks like: https://github.com/thuliteio/doks/blob/main/config/postcss.config.js |
Beta Was this translation helpful? Give feedback.
-
|
The Thulite/Hugo workflow is described here — I will add an updated version to the Doks docs: https://vermeer.thulite.io/docs/start-here/workflow/ So, |
Beta Was this translation helpful? Give feedback.
I took another swing at troubleshooting this and found a solution for the main issue. As mentioned in my previous comment, I'm a bit surprised to not see more discussions/issues about this since it happens in the default configuration of the template.
In
postcss.config.jsthere's a line that looks like this:const purgecss = require('@fullhuman/postcss-purgecss');. I changed it toconst purgecss = require('@fullhuman/postcss-purgecss').default;, and nownpm run buildworks without errors.Should the template be updated with this change?
I've also noticed the reason why none of the internal links worked when I ran
npm run preview. They all pointed tohttp://localhost:1313/, which is the ad…