npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

noscript-gen

v0.0.1

Published

SEO for JS sites with Puppeteer and jsdom pre-rendering

Downloads

6

Readme

noscript-gen

Better SEO for JS sites with Puppeteer and jsdom pre-rendering

The problem

A modern and dynamic JS Web App that must be wheel crawled and indexed by search engines (eg.: Google). Common SSR is not an option because it must be keeped client only (served by CDN) and updated with REST APIs.

Our solution

As Google recommends here:

https://support.google.com/webmasters/answer/66353?hl=en&ref_topic=6001971

"Place the same content from the JavaScript in a <noscript> tag. If you use this method, ensure the contents are exactly the same as what’s contained in the JavaScript, and that this content is shown to visitors who do not have JavaScript enabled in their browser."

Pre-render the site, get the rendered content and merge to original HTML file served to clients.

Technology stack

Reference

  • https://developers.google.com/web/tools/puppeteer/articles/ssr
  • https://github.com/jsdom/jsdom