You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 12, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 12, 2023. It is now read-only.
@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 lighthouse command is not found is that it's not in your $PATH. You can fix it like I wrote above:
you can add this:
"scripts": {
"lightcrawler": "lightcrawler"
}
to your package.json file
Then npm or yarn will look it up in node_module/.bin when you run yarn lightcrawler or npm run lightcrawler
Or you can install the package globaly with npm install lightcrawler -g as long as your global .node folder is in your '$PATH'.
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/
npm = v6.4.1
Anyways, now I'm not able to install lightcrawler.
$ npm install lightcrawler
lightcrawler@0.0.9
updated 1 package and audited 2987 packages in 3.853s
found 2 vulnerabilities (1 low, 1 critical)
run npm audit fix to fix them, or npm audit for details
$ npm audit fix
up to date in 2.697s
fixed 0 of 2 vulnerabilities in 2987 scanned packages
2 vulnerabilities required manual review and could not be updated
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 npm init to create a package.json file? Seems that most of the instructions (of the several projects I've investigated) make some pretty big assumptions about the knowledge base.
Adding the -g works mind you:
$ npm install lightcrawler -g
Anyways, hmm.. In a new directory, when I drop in the example from the install into a lightcrawler-config.json file then run:
Activity
alamowo commentedon Nov 5, 2018
you can add this:
to your package.json file
Then npm or yarn will look it up in
node_module/.binwhen you runyarn lightcrawlerornpm run lightcrawlermgifford commentedon Nov 5, 2018
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:
Create a lightcrawler-config.json file
Install the program - npm install --save-dev lightcrawler
Run the program - npm run lightcrawler --url https://atom.io/ --config lightcrawler-config.json
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.
alamowo commentedon Nov 5, 2018
@mgifford when you install the package with
npm install lightcrawlerthe package.json file is created in this folder for youalamowo commentedon Nov 5, 2018
@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
lighthousecommand is not found is that it's not in your$PATH. You can fix it like I wrote above:Or you can install the package globaly with
npm install lightcrawler -gas long as your global.nodefolder is in your '$PATH'.mgifford commentedon Nov 6, 2018
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/
npm = v6.4.1
Anyways, now I'm not able to install lightcrawler.
$ npm install lightcrawler
updated 1 package and audited 2987 packages in 3.853s
found 2 vulnerabilities (1 low, 1 critical)
run
npm audit fixto fix them, ornpm auditfor details$ npm audit fix
up to date in 2.697s
fixed 0 of 2 vulnerabilities in 2987 scanned packages
2 vulnerabilities required manual review and could not be updated
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
npm initto create a package.json file? Seems that most of the instructions (of the several projects I've investigated) make some pretty big assumptions about the knowledge base.Adding the -g works mind you:
$ npm install lightcrawler -g
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!