Fix: Paths for CLI to work on global as well as local installation. - Githubissues

GoogleChromeLabs / ps-analysis-tool

Privacy Sandbox Analysis Chrome Extension and CLI for analysis and understanding of cookie usage on web pages, and new privacy-preserving Chrome APIs

https://www.privacysandbox.com

Apache License 2.0

90 stars 18 forks source link

Fix: Paths for CLI to work on global as well as local installation. #727

Closed amovar18 closed 1 week ago

amovar18 commented 1 week ago

Description

This PR aims to make CLI work when its published on NPM as well as when the repository is cloned.

Relevant Technical Choices

Use different paths to get the CLI dependencies.

Testing Instructions

For local installation:

Clone this branch.
Go to terminal and run npm run build-cli.
Now run npm run cli https://natgeo.com
You should be able to see the report.

For global installation:

Go to terminal and run npm run local-registry:start && npm run publish:all:local.
Then open new terminal instance ther run npm i -g @google-psat/cli && psat https://bbc.com.
You should be able to see the report.

Additional Information:

Screenshot/Screencast

Checklist

[x] I have thoroughly tested this code to the best of my abilities.
[x] I have reviewed the code myself before requesting a review.
[x] This code is covered by unit tests to verify that it works as intended.
[x] The QA of this PR is done by a member of the QA team (to be checked by QA).