Browser Cant Display GULP SERVE SharePoint Workbench - sharepoint

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/"
}
}

Related

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?

nuxt.js localhost:3000 not running

As I'm currently going from React to Vue.js, i failed with running my localhost on Port 3000. Getting the below error message. Looks like there is a problem with the server.
Down below a added the installation process so that it gets clearer how it's installed.
Also you can find the error message when running npm run dev.
Any suggestions what the problem could be?
Installation process
create-nuxt-app v5.0.0
✨ Generating Nuxt.js project in cryptocheck24.org
? Project name: cryptocheck24.org
? Programming language: JavaScript
? Package manager: Npm
? UI framework: None
? Template engine: HTML
? Nuxt.js modules: (Press <space> to select, <a> to toggle all, <i> to invert se
lection)
? Linting tools: (Press <space> to select, <a> to toggle all, <i> to invert sele
ction)
? Testing framework: Jest
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Server (Node.js hosting)
? Development tools: (Press <space> to select, <a> to toggle all, <i> to invert
selection)
? Continuous integration: None
? Version control system: Git
Error message
> cryptocheck24.org#1.0.0 dev
> nuxt
╭───────────────────────────────────────╮
│ │
│ Nuxt # v2.15.8 │
│ │
│ ▸ Environment: development │
│ ▸ Rendering: server-side │
│ ▸ Target: server │
│ │
│ Listening: http://localhost:3000/ │
│ │
╰───────────────────────────────────────╯
ℹ Preparing project for development 16:25:39
ℹ Initial build may take a while 16:25:39
ℹ Discovered Components: .nuxt/components/readme.md 16:25:39
✔ Builder initialized 16:25:39
✔ Nuxt files generated 16:25:39
● Client █████████████████████████ compiling (0%)
◯ Server
node:internal/crypto/hash:67
this[kHandle] = new _Hash(algorithm, xofLen);
^
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:133:10)
at module.exports (/Users/remo/Desktop/cryptocheck24.org/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/Users/remo/Desktop/cryptocheck24.org/node_modules/webpack/lib/NormalModule.js:417:16)
at handleParseError (/Users/remo/Desktop/cryptocheck24.org/node_modules/webpack/lib/NormalModule.js:471:10)
at /Users/remo/Desktop/cryptocheck24.org/node_modules/webpack/lib/NormalModule.js:503:5
at /Users/remo/Desktop/cryptocheck24.org/node_modules/webpack/lib/NormalModule.js:358:12
at /Users/remo/Desktop/cryptocheck24.org/node_modules/webpack/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/Users/remo/Desktop/cryptocheck24.org/node_modules/webpack/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at Array.<anonymous> (/Users/remo/Desktop/cryptocheck24.org/node_modules/webpack/node_modules/loader-runner/lib/LoaderRunner.js:205:4) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
Since the v5, a Node v14 version is required: https://github.com/nuxt/create-nuxt-app/releases/tag/v5.0.0
So you can either try that. It works on my side with the latest LTS: Node v16.
Or fallback into using the v4 of the CLI.
That version runs perfectly for ages already
npx create-nuxt-app my-cool-app
and is well battle-tested!
PS: I've opened this issue btw: https://github.com/nuxt/create-nuxt-app/issues/1014

Module not found: Error: Cannot resolve 'file' or 'directory' ../../

i am new for nodejs, in my hybris project, first i installed nodejs, run 'npm install','npm i cross-env' commands, when i run the command 'npm run hybris' from node_module folder, i got some errors can you provide any solution.
C:\Atlas_Insta\hybris\bin\custom\rodanandfields\rodanandfieldsstorefront\FE-Develop>npm run hybris
> RodanAndFields#1.0.0 hybris C:\Atlas_Insta\hybris\bin\custom\rodanandfields\rodanandfieldsstorefront\FE-Develop
> cross-env NODE_ENV=production gulp hybris-build
[15:29:07] Using gulpfile C:\Atlas_Insta\hybris\bin\custom\rodanandfields\rodanandfieldsstorefront\FE-Develop\gulpfile.js
[15:29:07] Starting 'clean'...
[15:29:07] Finished 'clean' after 128 ms
[15:29:07] Starting 'markupCompile'...
[15:29:08] Starting 'sass'...
[15:29:09] Finished 'sass' after 615 ms
[15:29:09] Starting 'js'...
[15:29:09] Finished 'js' after 129 ms
[15:29:09] Starting 'copy-img'...
[15:29:09] Finished 'copy-img' after 584 μs
[15:29:09] Starting 'copy-fonts'...
[15:29:09] Finished 'copy-fonts' after 597 μs
[15:29:09] Starting 'copy-api'...
[15:29:09] Finished 'copy-api' after 630 μs
[15:29:09] Starting 'read-templates'...
[15:29:09] Finished 'read-templates' after 1.87 ms
All templates written successfully!
[15:29:32] Version: webpack 1.15.0
Asset Size Chunks Chunk Names
app.js 1.19 MB 0 [emitted] app
app.map 9.63 MB 0 [emitted] app
ERROR in C:/Atlas_Repo/bin/custom/rodanandfields/rodanandfieldsstorefront/FE-Develop/web/webroot/WEB-INF/r2/fe-components/checkout/order-summary/order-summary.js
Module not found: Error: Cannot resolve 'file' or 'directory' ../../../../../_ui/frontend/js/analytics/analytics-eventmap-r2 in C:\Atlas_Repo\bin\custom\rodanandfields\rodanandfieldsstorefront\FE-Develop\web/webroot/WEB-INF/r2/fe-components\checkout\order-summary
# C:/Atlas_Repo/bin/custom/rodanandfields/rodanandfieldsstorefront/FE-Develop/web/webroot/WEB-INF/r2/fe-components/checkout/order-summary/order-summary.js 23:30-103
ERROR in C:/Atlas_Repo/bin/custom/rodanandfields/rodanandfieldsstorefront/FE-Develop/web/webroot/WEB-INF/r2/fe-components/checkout/checkout-form-billing/checkout-form-billing.js
Module not found: Error: Cannot resolve 'file' or 'directory' ../../../../../_ui/frontend/js/analytics/analytics-config-r2 in C:\Atlas_Repo\bin\custom\rodanandfields\rodanandfieldsstorefront\FE-Develop\web/webroot/WEB-INF/r2/fe-components\checkout\checkout-form-billing
# C:/Atlas_Repo/bin/custom/rodanandfields/rodanandfieldsstorefront/FE-Develop/web/webroot/WEB-INF/r2/fe-components/checkout/checkout-form-billing/checkout-form-billing.js 23:22-93
Which Hybris version are you using? I had a smilar problem with hybris 6.6. It worked for me after I switch to node v6.14.3 I was using a more recent node with a more recent npm version.
I found this version inside the npmancillary extension's folder
ext-content/npmancillary/resources/npm/node

Heroku app successfully pushed but will not open

Below is the log when I deploy/push to Heroku. I'm very new to this and have tried extensive research on what could be the root error but alas, I must ask. I've had a running app on Heroku before, but I've made some changes locally and then deleted the Heroku app and decided to change the remote. Here is a link to my Github: https://github.com/tomtam6/tom-tam.git
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NPM_CONFIG_PRODUCTION=true
NODE_VERBOSE=false
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): 6.11.0
engines.npm (package.json): 3.10.10
Resolving node version 6.11.0...
Downloading and installing node 6.11.0...
npm 3.10.10 already installed with node
-----> Restoring cache
Loading 2 from cacheDirectories (default):
- node_modules (exists - skipping)
- bower_components (not cached - skipping)
-----> Building dependencies
Prebuild detected (node_modules already exists)
Rebuilding any native modules
body-parser#1.17.2 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/body-parser
bytes#2.4.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/bytes
content-type#1.0.2 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/content-type
debug#2.6.7 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/body-parser/node_modules/debug
ms#2.0.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/ms
depd#1.1.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/depd
http-errors#1.6.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/http-errors
inherits#2.0.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/inherits
setprototypeof#1.0.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/setprototypeof
statuses#1.3.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/statuses
iconv-lite#0.4.15 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/iconv-lite
on-finished#2.3.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/on-finished
ee-first#1.1.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/ee-first
qs#6.4.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/qs
raw-body#2.2.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/raw-body
unpipe#1.0.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/unpipe
type-is#1.6.15 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/type-is
media-typer#0.3.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/media-typer
mime-types#2.1.16 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/mime-types
mime-db#1.29.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/mime-db
cookie-parser#1.4.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/cookie-parser
cookie#0.3.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/cookie
cookie-signature#1.0.6 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/cookie-signature
debug#2.6.8 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/debug
ejs#2.5.6 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/ejs
express#4.15.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/express
accepts#1.3.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/accepts
negotiator#0.6.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/negotiator
array-flatten#1.1.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/array-flatten
content-disposition#0.5.2 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/content-disposition
debug#2.6.7 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/express/node_modules/debug
encodeurl#1.0.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/encodeurl
escape-html#1.0.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/escape-html
etag#1.8.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/etag
finalhandler#1.0.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/finalhandler
debug#2.6.7 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/finalhandler/node_modules/debug
parseurl#1.3.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/parseurl
fresh#0.5.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/fresh
merge-descriptors#1.0.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/merge-descriptors
methods#1.1.2 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/methods
path-to-regexp#0.1.7 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/path-to-regexp
proxy-addr#1.1.4 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/proxy-addr
forwarded#0.1.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/forwarded
ipaddr.js#1.3.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/ipaddr.js
range-parser#1.2.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/range-parser
send#0.15.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/send
debug#2.6.7 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/send/node_modules/debug
destroy#1.0.4 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/destroy
mime#1.3.4 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/mime
serve-static#1.12.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/serve-static
utils-merge#1.0.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/utils-merge
vary#1.1.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/vary
morgan#1.8.2 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/morgan
basic-auth#1.1.0 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/basic-auth
on-headers#1.0.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/on-headers
serve-favicon#2.4.3 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/serve-favicon
safe-buffer#5.0.1 /tmp/build_af04dccbe55a579f742b63b9b9775aa9/node_modules/safe-buffer
Installing any new modules (package.json)
-----> Caching build
Clearing previous node cache
Saving 2 cacheDirectories (default):
- node_modules
- bower_components (nothing to cache)
-----> Build succeeded!
-----> Discovering process types
Procfile declares types -> web
-----> Compressing...
Done: 14.9M
-----> Launching...
Released v4
https://tom-tam.herokuapp.com/ deployed to Heroku
When you check out your heroku desktop, in the "overview" tab for your app, does it show that your last build succeeded or failed?
And when you check out the logs, does it show the app is up and running?
--edit based on comment discussion--
Add this to app.js, before module.exports = app;
const PORT = process.env.PORT || 8000; app.listen(PORT, () => { console.log(`App listening on port ${PORT}!`); });

Upgrade graceful-fs module to a recent version

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

Resources