Help with NPM Start Command

[shanewin]

Just wondering if anyone is having a similar issue. My "npm start" gets hung up right here.

Thanks in advance, this program looks great.

% npm start

responsive-html-email-signature@6.2.0 start
./node_modules/.bin/gulp

Loading tasks from the "/tasks" directory...
Tasks loaded successfully.
gulpfile.js executed successfully.
[16:42:40] Using gulpfile ~/Desktop/e-sign-app/responsive-html-email-signature/gulpfile.js
[16:42:40] Starting 'default'...
[16:42:40] Starting 'run-pipeline'...
[16:42:40] Starting 'dupe'...
[16:42:40] Finished 'dupe' after 37 ms
[16:42:40] Starting 'less'...
[16:42:40] Finished 'less' after 4.98 ms
[16:42:40] Starting 'sass'...
[16:42:40] Starting 'dupe'...
[16:42:40] Finished 'dupe' after 12 ms
[16:42:40] Starting ''...
[16:42:40] Finished '' after 2.39 ms
[16:42:40] Finished 'sass' after 15 ms
[16:42:40] Starting 'postcss'...
[16:42:40] Finished 'postcss' after 29 ms
[16:42:40] Starting 'lint'...
[16:42:40] Finished 'lint' after 3.94 ms
[16:42:40] Starting 'build'...
[16:42:40] Finished 'build' after 3.11 ms
[16:42:40] Starting 'check-for-unused'...
[16:42:40] Finished 'check-for-unused' after 8.18 ms
[16:42:40] Finished 'run-pipeline' after 103 ms
[16:42:40] Starting ''...
Starting the default task...

[danmindru]

hi @shanewin!

Do you get anything in the dist directory?

By default the start command continues to watch your files for changes and recompiles the templates.
If you want to generate once and then exit you can run:

npm run once

hope this helps,
Dan

[shanewin]

Hi @danmindru -

That was very helpful! I am able to edit the templates folder and produce signatures in /dist . I guess I will just have to run 'npm run once' when I want to generate a new one.

Thank you!