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

@noths/storefront

v2.1.1

Published

storefront for noths partners

Downloads

13

Readme

Storefront

Storefront is a library to help rendering storefronts.

It is full SSR (server side rendering) "compliant" as it does work without having client side interfaces like window or document, either in the source code or in the build process, because we don't rely on any bundler like webpack for distributing the server-side code of the library. We only use it for development purposes and distributing the client side bundle.

This library was extracted from noths-storefront service. We maintained all the logic with new and updated dependencies. You can read more about it here.

How to start development with hot reload

Execute the commands below to start a development server.

npm i
npm run start

Now visit http://localhost:8080

It uses the files under the build-dev folder to serve a development version of it with mocked data.

How to prepare the library for server side usage and client side hydration

npm run build

The following will be available in the ./dist folder:

  • entire source code transpiled with babel so it can safely be used as a common-js module in a node js environment

  • entire source code worked and packed with webpack in the app.js

  • the assets like png's

  • the stylesheets from the app and styles-toolkit

How to publish the library

You'll need to register on npm by running npm adduser. If you're already registered on npm, use npm login instead.

In order to publish:

  • the version bump should be part of the pull request

  • after a successful merged pull request you will have to:

npm publish

How to use the library while doing server side rendering

npm i @noths/storefront
import { prepare } from '@noths/storefront'
// data as in the content that was fetched from the s3 bucket populated by https://github.com/notonthehighstreet/partner-content
const dataContainer = prepare(data)
// you can also use other functions from ReactDOMServer
// the resulting container should embeded in an html document
// for more info look at the example in https://notonthehighstreet.atlassian.net/wiki/spaces/T8B/pages/758349860/Storefront-frontend
ReactDOMServer.renderToString(dataContainer)

We can also see a working example in the index.js under ./build-dev folder.

How to use the library while doing client side rendering

  • declare the dependencies like app.js and stylesheets in the html file

Unit tests

npm run test

Tests with coverage

npm run test:coverage