-
Notifications
You must be signed in to change notification settings - Fork 3
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
Template generation failed #7
Comments
Thanks @aantron! I am not sure that's the root cause, but I just removed the pins in master. Would you mind trying the generation again? |
I now get to a second install (with
|
Could it be that you're running an "old" version of NodeJS? Tailwind requires Node 12.13 or higher (https://tailwindcss.com/docs/upgrading-to-v2#upgrade-to-node-js-12-13-or-higher) If this is the issue, I'll add a requirement section in the README, alongside the other suggestions laid down in #5 |
Also, the default choices shouldn't fail with this error, as they don't include TailwindCSS. Can you confirm that you explicitly chose to generate the TailwindCSS setup? |
Yes, I chose all options to exercise everything. |
I have Node 10.19.0 installed. Could you add the requirement, together with a link to instructions somewhere that show how to upgrade Node? I am using Node from Ubuntu 20.04, so this is a pretty aggressive constraint. |
I've added some instructions in the README, alongside with a recommendation to use Here are the commands to install it: # Install NVM
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
# Reload bash
source ~/.bashrc
# Install an NPM version, 14 is the latest LTS
nvm install 14
# Use the version in your current prompt
nvm use 14 |
These instructions don't work for fish, see nvm-sh/nvm#303. Looking for good workarounds. |
Arg.. I this case maybe the best method for you would be to upgrade your system node's version?
|
Template generation has now succeeded, thanks! |
I'm currently hitting the error below. I first reached this a few days ago, and I waited for the
dream-livereload
release in case that was the cause. However, this is still occurring afteropam update
and confirming that opam knows aboutdream-livereload
withopam list
.The text was updated successfully, but these errors were encountered: