-
Notifications
You must be signed in to change notification settings - Fork 98
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
Add Wappalyzer detection for Web Worker Offloading plugin #1597
Comments
Oh, woops. Not including a generator tag was an oversight. Let's add it. |
Since Web Worker Offloading is not yet featured in the Features screen in the latest version, there are very few installs of the plugin in the wild. This will change once we release the next version of PL, which would happen at the same time this meta tag from #1598 goes out. |
I'll create a sub-issue! |
@adamsilverstein I've opened #1598 to fix this already. |
Perfect, thanks! I can take care of adding the wappalyzer sniff |
I submitted a PR to add the Wappalyzer sniff: HTTPArchive/wappalyzer#71 |
PR was merged |
Feature Description
Now that https://wordpress.org/plugins/web-worker-offloading/ is live, we should add Wappalyzer detection for it. Opening this issue to track that work.
I noticed we didn't include a generator tag in this plugin, should we go ahead and add that?
Currently we could possibly detect usage with the
web-worker-offloading
path, but adding a generator tag would make detection cleaner. It might make sense to only add the generator tag when the worker strategy is actually used.cc: @westonruter
The text was updated successfully, but these errors were encountered: