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

@fuxifuchs/puppy-nest

v1.0.3

Published

ssr module implemented via puppeteer for usage in NestJS

Downloads

6

Readme

What is this?

This package is a NestJS Module which implements a simple SSR function to prerender any SPA via Puppeteer and return the rendered HTML back to the client. Because these are the times we live in :).

Why you would ever want to use this technique is perfectly described here by Eric Bidelman. Long story short, it takes very little changes to your SPA to make SSR work this way, without refactoring your SPA to some SSR Framework like NUXT or NEXT. You can even just serve the prerendered Markup to the google bot and let your users use the normal SPA.

In the example he uses express, but as I personally prefer NestJS and Typescript, thats how I implemented what he describes in the article.

Installation

You can add this Module to any Nest Application by installing it via Yarn

yarn add @fuxifuchs/puppy-nest

Afterwards all you need to do is import the module into your Application Module and you should be good to go.

import { Module } from '@nestjs/common';
import { RenderingModule } from '@fuxifuchs/puppy-nest';

@Module({
  imports: [RenderingModule],
})
export class AppModule {}

Usage

After installing the package and adding it to your Application Module you should see that there is a new route when running your Nest Application locally via:

yarn start:dev

There should be some console output looking like the following:

[Nest] 39175   - 2021-03-11 16:48:54   [RoutesResolver] RenderingController {/prerender}: +4ms
[Nest] 39175   - 2021-03-11 16:48:54   [RouterExplorer] Mapped {/prerender, GET} route +3ms

This means, that all went as expected and your application now accepts GET requests under the /prerender endpoint. This is coming straight from the Rendering.module. The /prerender endpoint needs to be called with a query param called url which specifies what Resource should be prerendered and a query param called selector which specifies which HTML Selector should be waited for and will return the rendered HTML and how long the Headless rendering took as response.

An example Request would look like this:

curl --location --request GET 'http://localhost:3000/prerender/?url=https://google.de&selector=body'

For any changes required to your SPA to make this technique work, please refer to the Article by Eric Bidelman as he already described what is necessary in great detail :).

License

Licensed under the MIT License - see the LICENSE file for details.