Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Considering the creation of an npm package or even to deploy on npmjs #72

Open
RignonNoel opened this issue Nov 3, 2024 · 2 comments
Open

Comments

@RignonNoel
Copy link

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

@tunetheweb
Copy link
Member

As noted in #52 (comment) we're not looking to main a replacement for Wappalyzer and are doing basic maintenance of this fork for our own needs.

@max-ostapenko
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants