Closed harisharjun closed 1 year ago
Please run this command before run project-setup
. it must work. thanks
Didn't help. I am getting the same error even after npm run project-setup
.
I said before, not after
I meant I tried it before only. This is the order in which I tried.
npm run project-setup
npm run remove-darkmode
But even after trying this, I am getting the same error.
I don't know man, I just tried it on my machine and other machines too. working perfectly. maybe your node version is not matching. try to install nodejs 18
I am on node v18.17.1
But still getting the same error.
In that case, you should remove dark-mode
manually, it's not that hard. I checked the script on every platform windows, linux, mac
and everywhere it works. I don't know what happened on your end. but I am pretty sure it's not the script issue. thanks
I ran into this as well.
Correct steps after a fresh git clone
of the hugoplate
repo to remove dark mode:
cd <reponame>
npm install
npm run remove-darkmode
npm run project-setup
If you forgot the npm install
first, you will have issues.
I did try the npm install but didn't work.
So, I manually changed the settings in the config file directly to remove the darkmode, and it worked!
Regards!
On Tue, Oct 31, 2023 at 9:26 AM Stacy Gaudreau @.***> wrote:
I ran into this as well.
Correct steps after a fresh git clone of the hugoplate repo to remove dark mode:
- cd
- npm install
- npm run remove-darkmode
- npm run project-setup
If you forgot the npm install first, you will have issues.
— Reply to this email directly, view it on GitHub https://github.com/zeon-studio/hugoplate/issues/38#issuecomment-1786398955, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASFEJ7J532BCSFDTFTTUKQTYCBZGTAVCNFSM6AAAAAA4NXHCP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBWGM4TQOJVGU . You are receiving this because you authored the thread.Message ID: @.***>
While I am running
npm run remove-darkmode
in the projects folder, I am getting this error:Please help me how to proceed. Unable to find any suitable resolution. I suspect it is something to do with my npm, but unable to resolve it...