Shutting down browsersync with CTRL+C #2003
Unanswered
dbraun-ascendium
asked this question in
Q&A
Replies: 1 comment
-
Furthermore..... here's the debug.log: 0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/Users/braund/homebrew/Cellar/node@14/14.17.0/bin/node',
1 verbose cli '/Users/braund/homebrew/Cellar/node@14/14.17.0/lib/node_modules/npm/bin/npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'watch:css'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prewatch:css', 'watch:css', 'postwatch:css' ]
5 info lifecycle [email protected]~prewatch:css: [email protected]
6 info lifecycle [email protected]~watch:css: [email protected]
7 verbose lifecycle [email protected]~watch:css: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~watch:css: PATH: /Users/braund/homebrew/Cellar/node@14/14.17.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/braund/Sites/parcel-jan-10/node_modules/.bin:/Users/braund/homebrew/Cellar/node@14/14.17.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/braund/Sites/parcel-jan-10/node_modules/.bin:/Users/braund/homebrew/Cellar/node@14/14.17.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/braund/Sites/parcel-jan-10/node_modules/.bin:/Users/braund/homebrew/opt/node@14/bin:/Users/braund/homebrew/bin:/Users/braund/.gem/ruby/2.6.0/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle [email protected]~watch:css: CWD: /Users/braund/Sites/parcel-jan-10
10 silly lifecycle [email protected]~watch:css: Args: [
10 silly lifecycle '-c',
10 silly lifecycle 'parcel watch src/scss/index.scss --dist-dir public/css --no-hmr'
10 silly lifecycle ]
11 silly lifecycle [email protected]~watch:css: Returned: code: 1 signal: null
12 info lifecycle [email protected]~watch:css: Failed to exec watch:css script
13 verbose stack Error: [email protected] watch:css: `parcel watch src/scss/index.scss --dist-dir public/css --no-hmr`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/Users/braund/homebrew/Cellar/node@14/14.17.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:376:20)
13 verbose stack at ChildProcess.<anonymous> (/Users/braund/homebrew/Cellar/node@14/14.17.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:376:20)
13 verbose stack at maybeClose (internal/child_process.js:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid [email protected]
15 verbose cwd /Users/braund/Sites/parcel-jan-10
16 verbose Darwin 22.2.0
17 verbose argv "/Users/braund/homebrew/Cellar/node@14/14.17.0/bin/node" "/Users/braund/homebrew/Cellar/node@14/14.17.0/lib/node_modules/npm/bin/npm-cli.js" "run" "watch:css"
18 verbose node v14.17.0
19 verbose npm v6.14.13
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] watch:css: `parcel watch src/scss/index.scss --dist-dir public/css --no-hmr`
22 error Exit status 1
23 error Failed at the [email protected] watch:css script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ] |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, this isn't entirely a browser-sync question, but I hope someone can help. I'm running brower-sync during development with parcel and eleventy. This seems to work fine for developing, and builds.
However, when I want to CTRL+C to "kill" everything, its messy. First attempt doesn't seem to do anything. Second attempt it throws an error in the command line. Usually on the 3rd attempt, I get my command prompt back.
Is there a different way to do this or something my inexperience with NPM scripts is missing? Here is what the error looks like with my package.json below that:
I am using Node v14.17.0
Beta Was this translation helpful? Give feedback.
All reactions