Information Security with HelmetJS - Hide Potentially Dangerous Information Using helmet.hidePoweredBy()

Information Security with HelmetJS - Hide Potentially Dangerous Information Using helmet.hidePoweredBy()
0

#1

Hi all,
I noticed that the helmetJS challenges have been discussed a couple of times but it’s unclear if tests are failing because of the Glitch template or if there is a problem with the browser of choice.

Users are reporting an intermittent behavior in validating the solution.

In addition to what has been already shared here, I also add the template, which comes with a package.json as

{
  "name": "fcc-infosec-challenges",
  "version": "0.0.1",
  "description": "fcc backend boilerplate",
  "main": "server.js",
  "scripts": {
    "start": "node myApp.js"
  },
  "dependencies": {
    "express": "^4.16.3",
    "helmet": "^3.13.0"
  },
  "engines": {
    "node": "4.4.5"
  },
  "keywords": [
    "node",
    "hyperdev",
    "express",
    "freecodecamp"
  ],
  "license": "MIT"
}

returns

Could not find node 4.4.5, using 8

Any idea how to make these challenges a little more “deterministic” :grinning: ?


[Done] Hide Potentially Dangerous Information Using helmet.hidePoweredBy()
#2

Hello Mauro,
as posted in this post reply it seems like these logs could be from pasting code into package.json which shouldn’t be done because of the text format.
I know it’s been long while but I had this issue and found nobody answered.
happy coding!