Upgrade graceful-fs module to a recent version - node.js

i've a docker container from node:6 official image.
I'd like trying this project: https://github.com/mozilla/fxa-webrtc-idp
node version is 6.9.5
npm version is 3.10.10
when i exec npm test, this is what appairs:
root#3be6ee5c1ab6:/fxa-webrtc-idp# npm test
npm info it worked if it ends with ok
npm info using npm#3.10.10
npm info using node#v6.9.5
npm info lifecycle fxa-webrtc-idp#0.64.0~pretest: fxa-webrtc-idp#0.64.0
npm info lifecycle fxa-webrtc-idp#0.64.0~test: fxa-webrtc-idp#0.64.0
> fxa-webrtc-idp#0.64.0 test /fxa-webrtc-idp
> LOG_LEVEL=error grunt test --node-env=test
(node:354) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Running "copyright:app" (copyright) task
Running "eslint:files" (eslint) task
Running "mochaTest:test" (mochaTest) task
the route /sign
✓ returns a 401 when the request is not authenticated
✓ returns a signed assertion when the request is authenticated
the route /
✓ should return version information
the route /__version__
✓ should return version information
4 passing (44ms)
Running "mochaTest:coverage" (mochaTest) task
Coverage Summary:
Name Stmts Miss Cover Missing
-----------------------------------------------------------
lib/app.js 22 0 100%
lib/logging/summary.js 14 3 79% 14,30,31
lib/routes/index.js 1 0 100%
lib/routes/oauthBegin.js 7 2 71% 20,25
lib/routes/oauthComplete.js 8 2 75% 18,24
lib/routes/sign.js 10 0 100%
lib/routes/verify.js 16 9 44% 14,23,26,27,29,31,32,35,37
lib/routes/version.js 52 8 85% 34,35,47,48,60,61,74,75
===========================================================
TOTAL 130 24 82%
Running "mochaTest:travis-cov" (mochaTest) task
Coverage: 81%
Code coverage below threshold: 81 < 95
Execution Time (2017-02-08 11:46:19 UTC)
loading tasks 1s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 58%
eslint:files 432ms ▇▇▇▇▇▇▇▇▇▇▇▇ 25%
mochaTest:test 287ms ▇▇▇▇▇▇▇▇ 16%
Total 1.8s
npm info lifecycle fxa-webrtc-idp#0.64.0~test: Failed to exec test script
npm ERR! Test failed. See above for more details.
When i exec npm ls graceful-fs this is what appairs:
root#3be6ee5c1ab6:/fxa-webrtc-idp# npm ls graceful-fs
npm info it worked if it ends with ok
npm info using npm#3.10.10
npm info using node#v6.9.5
fxa-webrtc-idp#0.64.0 /fxa-webrtc-idp
+-- grunt#0.4.5
| `-- glob#3.1.21
| `-- graceful-fs#1.2.3
+-- grunt-conventional-changelog#5.0.0
| `-- conventional-changelog#0.5.3
| `-- read-pkg#1.1.0
| +-- load-json-file#1.1.0
| | `-- graceful-fs#4.1.11
| `-- path-type#1.1.0
| `-- graceful-fs#4.1.11
+-- grunt-eslint#17.3.1
| `-- eslint#1.10.3
| `-- file-entry-cache#1.3.1
| `-- flat-cache#1.2.2
| `-- graceful-fs#4.1.11
+-- grunt-jscs#2.7.0
| `-- jscs#2.9.0
| `-- babel-jscs#2.0.5
| `-- babel-core#5.8.38
| +-- output-file-sync#1.1.2
| | `-- graceful-fs#4.1.11
| `-- regenerator#0.8.40
| `-- commoner#0.10.8
| `-- graceful-fs#4.1.11
+-- grunt-nodemon#0.4.1
| `-- nodemon#1.11.0
| +-- chokidar#1.6.1
| | `-- readdirp#2.1.0
| | `-- graceful-fs#4.1.11
| `-- update-notifier#0.5.0
| `-- configstore#1.4.0
| +-- graceful-fs#4.1.11
| `-- write-file-atomic#1.3.1
| `-- graceful-fs#4.1.11
`-- grunt-nsp#2.1.2
`-- nsp#2.0.1
`-- nodesecurity-npm-utils#3.0.0
`-- silent-npm-registry-client#1.0.0
`-- npm-registry-client#6.3.3
`-- graceful-fs#3.0.8
npm info ok
How can i solve my problem? Thanks for the support

Try upgrading your npm. It might help, like it did for me with similar kind of error. Please run below command and
npm install npm#latest -g

Related

Playwright tests are not running on gitlab CICD

Hello,
While my Playwright tests are running perfectly on my local machine, on a remote gitlab machine they all fail.
The output looks like this:
$ cd playwright
$ npm ci
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
> cd .. && husky install front/.husky
husky - Git hooks installed
added 236 packages, and audited 237 packages in 25s
70 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
$ npx playwright install
Downloading Chromium 105.0.5195.19 (playwright build v1019)...
| | 0% of 133.2 Mb
|■■■■■■■■ | 10% of 133.2 Mb
|■■■■■■■■■■■■■■■■ | 20% of 133.2 Mb
|■■■■■■■■■■■■■■■■■■■■■■■■ | 30% of 133.2 Mb
|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 40% of 133.2 Mb
|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 50% of 133.2 Mb
|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 60% of 133.2 Mb
|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 70% of 133.2 Mb
|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 80% of 133.2 Mb
|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ | 90% of 133.2 Mb
|■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| 100% of 133.2 Mb
Chromium 105.0.5195.19 (playwright build v1019) downloaded to /ms-playwright/chromium-1019
$ npm run ci:test
npx playwright test --config=src/configs/playwright.prod.config.ts
Running 30 tests using 10 workers
and then a bunch of red tests names lines indicating failure:
✘ 2 [chromium] › account-settings.test.ts:12:3 › Account Settings functionality › validate account timezone modification (50s)
✘ 3 [chromium] › account-settings.test.ts:16:3 › Account Settings functionality › validate adding api key (50s)
page.goto: Timeout 50000ms exceeded.
7 | test.describe('Account Settings functionality', () => {
8 | test('validate account phone number modification', async ({ page }) => {
> 9 | await validateChangePhoneNumber({ page });
| ^
10 | });
...
29 failed
at Object.Account Settings (/builds/dashboard-client/playwright/src/support/navigate/navigateToPage.ts:91:28)
at navigationByPageName (/builds/dashboard-client/playwright/src/support/navigate/navigateToPage.ts:102:10)
at validateChangeTimezone (/builds/dashboard-client/playwright/src/support/validate/validateAccountSettings/validateChangeTimezome.ts:12:9)
at /builds/dashboard-client/playwright/src/tests/account-settings.test.ts:13:11
By looking at the recording it seems that the app is opened but no navigation step occurres until timeout exceeds.
The dependencies for Playwright are missing as indicated by the 'Downloading Chromium' progress indicators.
According to the documentation npx playwright install --with-deps will install the deps. Refer to: https://playwright.dev/docs/ci.

the vue-awesome-swiper dependency was not found

I tried to use swiper plugin on my nuxtjs project. But I've got error on my command line when I running "yarn run dev":
`
yarn run dev
yarn run v1.22.19
$ nuxt
WARN sass-loader#13.1.0 is installed but ^10.1.1 is expected
╭───────────────────────────────────────╮
│ │
│ Nuxt # v2.15.8 │
│ │
│ ▸ Environment: development │
│ ▸ Rendering: server-side │
│ ▸ Target: server │
│ │
│ Listening: http://localhost:3000/ │
│ │
╰───────────────────────────────────────╯
i Preparing project for development
i Initial build may take a while
√ Builder initialized
√ Nuxt files generated
* Client █████████████████████████ building (39%) 245/251 modul
es 6 active
node_modules\setimmediate\setImmediate.js
× Server
Compiled with some errors in 9.04s
× Client
Compiled with some errors in 10.53s
× Server
Compiled with some errors in 9.04s
ERROR Failed to compile with 1 errors
This dependency was not found:
* vue-awesome-swiper/dist/ssr in ./plugins/swiper.js
To install it, you can run: npm install --save vue-awesome-swiper/dist/ssr
i Waiting for file changes
i Memory usage: 143 MB (RSS: 232 MB)
i Listening on: http://localhost:3000/
WARN Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'
`
vue-awesome-swiper does not detected while I've installed by "yarn add vue-awesome-swiper".
And I've followed this instruction on cmd:
npm install --save vue-awesome-swiper/dist/ssr
i Waiting for file changes
i Memory usage: 143 MB (RSS: 232 MB)
i Listening on: http://localhost:3000/
But still have issued on my code. Does anyone have same problems and had solution?

Appflow with cordova detects capacitor instead in build

I have a project that used to use capacitor but now uses only cordova.
Upon versioning it to a Commit in my Ionic Dashboard, I attempted to create a Build from this Commit and received this error
[13:57:35]: --------------------------------
[13:57:35]: --- Step: detect_native_type ---
[13:57:35]: --------------------------------
[13:57:35]: Checking if cordova or capacitor project
[13:57:35]: Capacitor project with TS/JS config detected
[13:57:35]: --------------------------------
[13:57:35]: --- Step: dependency_install ---
[13:57:35]: --------------------------------
[13:57:35]: Installing Dependencies
[13:57:35]: $ npm ci --quiet --no-optional
[13:58:03]: ▸ > core-js#3.17.3 postinstall /builds/project-0/node_modules/core-js
[13:58:03]: ▸ > node -e "try{require('./postinstall')}catch(e){}"
[13:58:04]: ▸ > core-js#3.6.4 postinstall /builds/project-0/node_modules/#angular-devkit/build-angular/node_modules/core-js
[13:58:04]: ▸ > node -e "try{require('./postinstall')}catch(e){}"
[13:58:04]: ▸ > sharp#0.25.4 install /builds/project-0/node_modules/sharp
[13:58:04]: ▸ > (node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)
[13:58:04]: ▸ info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.9.1/libvips-8.9.1-linux-x64.tar.gz
[13:58:06]: ▸ > #angular/cli#9.1.15 postinstall /builds/project-0/node_modules/#angular/cli
[13:58:06]: ▸ > node ./bin/postinstall/script.js
[13:58:07]: ▸ added 2108 packages in 31.198s
[13:58:07]: -------------------------------------
[13:58:07]: --- Step: create_capacitor_config ---
[13:58:07]: -------------------------------------
[13:58:09]: -------------------------
[13:58:09]: --- Step: upload_logs ---
[13:58:09]: -------------------------
[13:58:17]: Unable to upload npm package list log. Skipping.
+------------------+-----------------------+
| Lane Context |
+------------------+-----------------------+
| DEFAULT_PLATFORM | ios |
| PLATFORM_NAME | android |
| LANE_NAME | android package_build |
+------------------+-----------------------+
[13:58:20]: Capacitor config command failed, ensure capacitor dependency has been updated to version 3 or more
+------+-------------------------+-------------+
| fastlane summary |
+------+-------------------------+-------------+
| Step | Action | Time (in s) |
+------+-------------------------+-------------+
| 1 | default_platform | 0 |
| 2 | build_summary | 0 |
| 3 | add_git_credentials | 0 |
| 4 | get_appflow_config | 0 |
| 5 | detect_native_type | 0 |
| 6 | dependency_install | 31 |
| 💥 | create_capacitor_config | 2 |
| 8 | upload_logs | 11 |
+------+-------------------------+-------------+
[13:58:20]: fastlane finished with errors
/usr/local/bundle/bin/fastlane: [!] Capacitor config command failed, ensure capacitor dependency has been updated to version 3 or more (RuntimeError)
/usr/local/bundle/gems/fastlane-2.179.0/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in `shell_error!': Shell command exited with exit status 1 instead of 0. (FastlaneCore::Interface::FastlaneShellError)
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/helper/sh_helper.rb:80:in `sh_control_output'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/helper/sh_helper.rb:12:in `sh'
from /builds/project-0/fastlane/actions/create_capacitor_config.rb:13:in `run'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
from Fastfile:162:in `block (2 levels) in parsing_binding'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/lane.rb:33:in `call'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
from /usr/local/bundle/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
from /usr/local/bundle/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
from /usr/local/bundle/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
from /usr/local/bundle/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
from /usr/local/bundle/gems/fastlane-2.179.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in `take_off'
from /usr/local/bundle/gems/fastlane-2.179.0/bin/fastlane:23:in `<top (required)>'
from /usr/local/bundle/bin/fastlane:23:in `load'
from /usr/local/bundle/bin/fastlane:23:in `<main>'
What makes this error so odd is that every mention of 'capacitor' has been removed from my project including the capacitor.config.json file.
My ionic.config.json setup looks like this
"integrations": {
"cordova": {}
},
On top of that, I removed the package-lock.json and /node_modules and reinstalled, and then I ionic cordova platform add/remove ios & android and then 1ionic cordova prepare` ios & android.
Still, I receive this error.
Could anyone help me remove capacitor from my Build process in ionic dashboard
This is a known issue from Ionic and the solution is to contact Ionic and have them properly switch the account to capacitor or cordova. Solution 2 is that you need to create a new project on ionic with cordova or capacitor and then clone your project to it.

How to using docker-compose with environment

I have node application that build into an image. This image not contain .env file because I add it on .gitignore whereas the application need it. How can I configure this environment on docker-compose?
I've read some of example but still dont get it. This question has same problem with me but it still doesn't work.
docker-compose:
version: "3.7"
services:
node:
container_name: node-app
image: node_app:latest
ports:
- 3334:3333
environment:
- HOST=127.0.0.1
- PORT=3333
- NODE_ENV=dummy
- APP_NAME=AdonisJs
- CACHE_VIEWS=false
- DB_CONNECTION=mysql
- DB_HOST=127.0.0.1
- DB_PORT=3306
- DB_USER=root
- DB_PASSWORD=password
- DB_DATABASE=database
Dockerfile:
FROM node:14
WORKDIR /usr/src/app
COPY package*.json ./
RUN npm i -g #adonisjs/cli
RUN npm install
ENV HOST=0.0.0.0
COPY . .
EXPOSE 3333
CMD [ "node", "server.js" ]
Everytime I run docker-compose up its ended up with this.
WARNING: The HOST variable is not set. Defaulting to a blank string.
WARNING: The PORT variable is not set. Defaulting to a blank string.
Recreating node-app_node_1 ... done
Attaching to node-app_node_1
node_1 |
node_1 | Error: ENOENT: no such file or directory, open '/usr/src/app/.env'
node_1 |
node_1 |
node_1 | 1 Env.load
node_1 | /usr/src/app/node_modules/#adonisjs/framework/src/Env/index.js:110
node_1 |
node_1 | 2 new Env
node_1 | /usr/src/app/node_modules/#adonisjs/framework/src/Env/index.js:42
node_1 |
node_1 | 3 Object.closure
node_1 | /usr/src/app/node_modules/#adonisjs/framework/providers/AppProvider.js:29
node_1 |
node_1 | 4 Ioc._resolveBinding
node_1 | /usr/src/app/node_modules/#adonisjs/fold/src/Ioc/index.js:231
node_1 |
node_1 | 5 Ioc.use
node_1 | /usr/src/app/node_modules/#adonisjs/fold/src/Ioc/index.js:731
node_1 |
node_1 | 6 AppProvider.boot
node_1 | /usr/src/app/node_modules/#adonisjs/framework/providers/AppProvider.js:337
node_1 |
node_1 | 7 anonymous
node_1 | /usr/src/app/node_modules/#adonisjs/fold/src/Registrar/index.js:147
node_1 |
node_1 | 8 arrayMap
node_1 | /usr/src/app/node_modules/lodash/lodash.js:653
node_1 |
node-app_node_1 exited with code 1
All I know that docker-compose environment pass to the variable that called just as same as we define to get the value, but there is not .env file on the image to called the variable. What I have to do to make the docker-compose can pass the environment to the app? Any suggestion will be appreciated.
ENOENT indicates that node is looking for a file at /usr/src/app/.env but there is nothing there. Try adding
RUN touch /usr/src/app/.env
to your Dockerfile and see if having an empty .env file fixes it.

Browser Cant Display GULP SERVE SharePoint Workbench

Browser Cant Display GULP SERVE SharePoint Workbench
I am trying to create a SharePoint 2016 web-part using Visual Studio CODE (version 1.22.2) and I've been struggling to get the dev environment to work in both Windows 7 and Windows Server 2012 R2 (exact same setup works fine on Windows 10). Right now, I'm focusing on the Windows Server 2012 environment, since I have a little more control there...
To give a bit of background:
* Windows 10 Machine: Personal machine I built myself, I am Administrator, all features work as expected.
* Windows Server 2012 R2: Work Machine, I have to live with what I have. I am a local administrator but cannot install anything... All of the existing apps were installed by administrators who used pre-packaged deployment tools. There are some (unknown) security restrictions in place (probably group policies) that may be causing problems.
* Windows 7: Work Machine, I have to live with what I have. I am now a local administrator but all of the existing apps were installed by someone else using pre-packaged deployment tools... There are some (unknown) security restrictions in place (probably group policies) that may be causing problems.
I had to fight just to get the environment to use the "yo #microsoft/sharepoint" command...
Then I had to fight just to get gulp to run (it was saying sp-build-web was not installed even though it was...)
Now I cannot get a browser to actually reach the gulp serve.
-Yes, I tried the "$env:NODE_NO_HTTP2=1" command.
-Yes I also used the "gulp trust-dev-cert" command
Internet Explorer 11 only shows:
This page can't be displayed
* Make sure the web address https://localhost:5432 is correct.
* Look for the page with your search engine.
* Refresh the page in a few minutes.
Chrome displays a similar error.
I've run out of ideas. I don't see any errors below I can continue to follow up on...
Can someone help please?
I have NodeJS v9.4.0 installed and the following npm packages:
PS C:\code\VSCode\amtdHeadlines_untethered> npm list -g --depth=0
C:\Users\UName\AppData\Roaming\npm
+-- #microsoft/generator-sharepoint#1.4.1
+-- #microsoft/sp-build-web#1.4.1
+-- #microsoft/sp-client-base#1.0.0
+-- #microsoft/sp-client-preview#1.4.1
+-- #microsoft/sp-core-library#1.4.1
+-- #microsoft/sp-module-interfaces#1.4.1
+-- #microsoft/sp-page-context#1.4.1
+-- #microsoft/sp-webpart-base#1.4.1
+-- #microsoft/sp-webpart-workbench#1.4.1
+-- #types/chai#4.1.3
+-- #types/mocha#5.2.0
+-- ajv#6.4.0
+-- ansi-regex#2.1.1
+-- balanced-match#1.0.0
+-- brace-expansion#1.1.11
+-- code-point-at#1.1.0
+-- compass#0.1.1
+-- concat-map#0.0.1
+-- console-control-strings#1.1.0
+-- express#4.16.3
+-- generator-aspnet#0.3.3
+-- generator-code#1.1.30
+-- generator-hottowel#0.6.1
+-- generator-webapp#3.0.1
+-- graceful-fs#4.1.11
+-- grunt#1.0.2
+-- gulp#4.0.0
+-- inherits#2.0.3
+-- is-fullwidth-code-point#1.0.0
+-- minimatch#3.0.4
+-- minimist#0.0.8
+-- minipass#2.2.4
+-- mkdirp#0.5.1
+-- mocha#5.1.1
+-- ncu#0.2.1
+-- npm#6.0.0
+-- npm-check-updates#2.14.2
+-- number-is-nan#1.0.1
+-- office-ui-fabric-js#1.5.0
+-- office-ui-fabric-react#5.94.0
+-- once#1.4.0
+-- react#16.3.2
+-- react-addons-update#15.6.2
+-- react-dom#16.3.2
+-- request#2.85.0
+-- safe-buffer#5.1.2
+-- string-width#1.0.2
+-- strip-ansi#3.0.1
+-- wrappy#1.0.2
+-- yallist#3.0.2
+-- yarn#1.6.0
`-- yo#2.0.2
PS C:\code\VSCode\amtdHeadlines_untethered> gulp serve
Build target: DEBUG
[17:34:15] Using gulpfile C:\code\VSCode\amtdHeadlines_untethered\gulpfile.js
[17:34:15] Starting gulp
[17:34:15] Starting 'serve'...
[17:34:15] Starting subtask 'pre-copy'...
[17:34:15] Finished subtask 'pre-copy' after 8.26 ms
[17:34:15] Starting subtask 'copy-static-assets'...
[17:34:15] Starting subtask 'sass'...
[17:34:16] Finished subtask 'sass' after 904 ms
[17:34:16] Starting subtask 'tslint'...
[17:34:16] Starting subtask 'typescript'...
[17:34:16] [typescript] TypeScript version: 2.2.2
[17:34:16] Finished subtask 'copy-static-assets' after 939 ms
[17:34:18] Finished subtask 'tslint' after 1.45 s
[17:34:18] Finished subtask 'typescript' after 1.45 s
[17:34:18] Starting subtask 'ts-npm-lint'...
[17:34:18] Finished subtask 'ts-npm-lint' after 8.62 ms
[17:34:18] Starting subtask 'api-extractor'...
[17:34:18] Finished subtask 'api-extractor' after 1.33 ms
[17:34:18] Starting subtask 'post-copy'...
[17:34:18] Finished subtask 'post-copy' after 700 μs
[17:34:18] Starting subtask 'collectLocalizedResources'...
[17:34:18] Finished subtask 'collectLocalizedResources' after 5.07 ms
[17:34:18] Starting subtask 'configure-webpack'...
[17:34:18] Finished subtask 'configure-webpack' after 504 ms
[17:34:18] Starting subtask 'webpack'...
(node:6804) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https
://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
[17:34:19] Finished subtask 'webpack' after 676 ms
[17:34:19] Starting subtask 'configure-webpack-external-bundling'...
[17:34:19] Finished subtask 'configure-webpack-external-bundling' after 1.14 ms
[17:34:19] Starting subtask 'copy-assets'...
[17:34:19] Finished subtask 'copy-assets' after 63 ms
[17:34:19] Starting subtask 'write-manifests'...
[17:34:19] Finished subtask 'write-manifests' after 407 ms
[17:34:19] Starting subtask 'serve'...
Starting api server on port 5432.
Registring api: /getwebparts
Registring api: /.
Registring api: /workbench
[17:34:20] Finished subtask 'serve' after 483 ms
[17:34:20] Finished 'serve' after 4.61 s
(node:6804) ExperimentalWarning: The http2 module is an experimental API.
[17:34:20] Server started https://localhost:4321
[17:34:20] LiveReload started on port 35729
[17:34:20] Opening https://localhost:5432/workbench using the default OS app
Request: [::1] '/workbench'
[17:34:20] ==================[ Finished ]==================
[17:34:21] Project amtd-headlines-untethered version: 0.0.1
[17:34:21] Build tools version: 2.5.3
[17:34:21] Node version: v9.4.0
[17:34:21] Total duration: 7.79 s
Free the port 5432 since it is probably being used by another process.
Alternatively serve the application using a different config.
Go to 'config.serve.js' and change the port to your preferred port e.g. from '5432' to '8080' as follows:
{
"$schema": "https://developer.microsoft.com/json-schemas/core-
build/serve.schema.json",
"port": 4321,
"https": true,
"initialPage": "https://localhost:8080/workbench",
"api": {
"port": 8080,
"entryPath": "node_modules/#microsoft/sp-webpart-workbench/lib/api/"
}
}

Resources