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
Is your feature request related to a problem? Please describe.
Wappalyzer was easy to install with an npmjs package, since the fork is created, it seems that there is no package available on npmjs, forcing people to install from source.
Describe the solution you'd like
We could deploy the package on npmjs to make it easy for new users, enhance the visibility and attract potential new contributors
We have a PR #5 with NPM CLI package (seems identical to the mentioned one).
I think it can indeed make the rules development process easier for HTTP Archive purposes.
But I'm not sure publishing it on npm.js will increase the number and quality of technologies.
Is your feature request related to a problem? Please describe.
Wappalyzer was easy to install with an npmjs package, since the fork is created, it seems that there is no package available on npmjs, forcing people to install from source.
Describe the solution you'd like
We could deploy the package on npmjs to make it easy for new users, enhance the visibility and attract potential new contributors
Describe alternatives you've considered
Seems like there is an npmjs package, but it look like a random creation from a random guy that is not related to HTTPArchive contributions: https://www.npmjs.com/package/wappalyzer-zeeshan
Additional context
None
The text was updated successfully, but these errors were encountered: