It’s Next.js Liberation Day.
The #1 request we kept hearing: help us run Next fast and secure, without the lock-in and the costs.
So we did it. We kept the amazing DX of @nextjs, without the bespoke tooling, built on @vite. We’re working with other providers to make deployment a first-class experience everywhere.
Next.js belongs to everyone.
blog.cloudflare.com/vinext/
Hey @Wappalyzer, I'm starting to see CMS data combo WordPress + Squarespace now - I don't think a webpage can be both... is this an issue with the Chrome extension?
I absolutely love the wappalyzer.com chrome extension. I find it helpful in finding the tools and stacks other websites use and develop with.
For example, in my portfolio site garzn.com, it looks like this:
Who else is using @Wappalyzer ?
Why is @Wappalyzer tech stack detection so flaky? cmon, just look at the url please, just from that you can already detect the auth provider... maybe I should just build a better alternative
@Bovelett@greyd_suite Looks like the user base size didn't meet our threshold for inclusion but I'll get the team to include it anyway. Might take a few weeks.
@Wappalyzer@greyd_suite This is why I’m contacting you here. I was asking them about it, and they told me they filled that out twice now, but never got a response.
@Wappalyzer is the best product with the worst name. I have to search for another tool "build with" on google and search for the tool. Even writing this tweet i have to cross-check multiple time.