-
Notifications
You must be signed in to change notification settings - Fork 139
lightcrawler: command not found #15
Comments
you can add this: "scripts": {
"lightcrawler": "lightcrawler"
} to your package.json file |
Can you add this all to a single install file? Should be simpler to get to a point when you can run this. Things like:
Am I missing something here? Do I need to create a directory and stick in a package.json file somewhere? I'm not getting very far. Sorry. |
@mgifford when you install the package with |
@mgifford as a Drupal Buddy I can walk you through the process on a different channel (PM, Slack, E-Mail, you name it) For this issue, I think it's not a problem of this package. The reason the
Or you can install the package globaly with |
Hey thanks so @aharshbe really appreciate the Drupal community support. Ultimately I want to be able to run this along with automated testing on core. We haven't had a good means to do that, but think that lighthouse has some means to help us do a better job. I had to nix my node/npm system entirely as I was getting stuck in too many spaces. Did an install on my Mac from https://nodejs.org/en/ Anyways, now I'm not able to install lightcrawler. $ npm install lightcrawler
$ npm audit fix Although I did find a lightcrawler-config.json file where I tried to install it previously. I hadn't realized it would drop a json file there. There's definitely stuff I'm not getting about node.js. Do I need to run Anyways, hmm.. In a new directory, when I drop in the example from the install into a lightcrawler-config.json file then run: $ lightcrawler -u https://openconcept.ca -c lightcrawler-config.json It seems to be working.. I'll reach out in the Drupal world and find you there. This might be worked through though. Thanks! |
It seems to install fine, but.
$ npm install lightcrawler
updated 1 package and audited 789 packages in 2.884s
found 0 vulnerabilities
$ lightcrawler --url https://atom.io/ --config lightcrawler-config.json
-bash: lightcrawler: command not found
The text was updated successfully, but these errors were encountered: