You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: I am doing this in VS Code not Visual Studio.
On a clean machine with not much installed beyond VS Code setup with my short-list of required extensions, I wanted to kick the tired on nvQT-Tw. Hopefully these problems and solutions can be turned in to improved defaults or config changes so other avoid these "speed bumps."
add to package.json, "gulp-cli": "^2.3.0", (and re-run npm install)
The gulp@4 docs seem to recommend installing gulp-cli globally. So since its really not a dev dependency, maybe just include setup requirements, have the user verify both Gulp and Gulp-CLI are installed by typing > gulp --v
Checked docs on gulp-jshint@2 and it does say the install is now, npm install jshint gulp-jshint --save-dev - so you just need to add "jshint": "^2.13.4", to package.json.
Other
Also, I have a suggestion, a lot of folks (like me) expect to type npm run build and npm run watch - so maybe update package.json:
Note: I am doing this in VS Code not Visual Studio.
On a clean machine with not much installed beyond VS Code setup with my short-list of required extensions, I wanted to kick the tired on nvQT-Tw. Hopefully these problems and solutions can be turned in to improved defaults or config changes so other avoid these "speed bumps."
For David P, here is a link to our Slack convo in case there is a detail or context there that I left out.
First bump:
After running
npm install
, tryinggulp
(orgulp build
) simply results ingulp: The term 'gulp' is not recognized as...
To fix this either:
npm install -g gulp-cli
"gulp-cli": "^2.3.0",
(and re-run npm install)The gulp@4 docs seem to recommend installing gulp-cli globally. So since its really not a dev dependency, maybe just include setup requirements, have the user verify both Gulp and Gulp-CLI are installed by typing
> gulp --v
Second bump
Then running
gulp build
results in:Checked docs on gulp-jshint@2 and it does say the install is now,
npm install jshint gulp-jshint --save-dev
- so you just need to add"jshint": "^2.13.4",
to package.json.Other
Also, I have a suggestion, a lot of folks (like me) expect to type
npm run build
andnpm run watch
- so maybe update package.json:Further, if you want to completely avoid the Gulp-CLI thing, add a "preinstall" script like this:
Then Gulp-CLI gets installed (or updated) globally during
npm install
.You can check out my fork here, https://github.com/jeremy-farrance/nvQuickTheme-Tailwind
The text was updated successfully, but these errors were encountered: