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

proxy-seller-ssr-test-1

v1.0.1

Published

Installer for SSR app

Downloads

3

Readme

Private NPX Module, SSR module

Private SSR

ReactJS: 18, Webpack: 5 Install project: yarn install, yarn add -D copy-webpack-plugin Start project: yarn ssr:start

Introduction

Common

It has a location file that can be used to define a language or country. It includes the alfa2 and alfa3 country code, the language abbreviation and the full country name.

Config

This folder includes the webpack config of the application. What you need to know:

  1. The path.js file: it stores the paths to the build, public src, package.json, etc. directories. Once you open it, you can read it in detail.

ENV

A place where global reusable variables that can be used for both development or production depending on the command you run.

Public

The place where you granite your fonts pictures etc. After you use the command to start SSR this data will be added to the build folder. The place where you granite your fonts pictures etc. After you use the command to start SSR this data will be added to the build folder. For static display they will be used from there.

Scripts

This is the directory that is responsible for running the webpack configuration and for running SSR.

Server

This is the SSR directory. For your development, you need to make modifications to config.ssr.js. It contains:

  1. backEndHealthCheck: responsible for whether you need to wait for the backend to be raised before running SSR. An example of the data to be transferred is given in the candy. We can use an additional callback if you want.
  2. seo: this object is used to set the default seo data or the data you can get from response.
  3. metaTags: this object is used to set the default meta data or the data you can get from a query.
  4. rewriteRules: .... robot.txt, default xml data from backend
  5. redirectData: this object is used to set the faulty language and redirect link.
  6. allowRoutes: specify in this object those pages that are used in your application (without specifying languages, just basic page designations).
  7. translations: an object with translations, you can see how it should look like in /src/store/translation/translation/translation.slice.js.
  8. checkConfig: ...
  9. routes: this is an array of paths that are in your application. You specify them in the src/routes folder. The example application shows how this is specified. src/routes/app.routes.js src/routes/app.routes.ssr.js
  10. storeConfig: here you must pass the APP and the store you created to redux in order to connect your application to the server and to ensure that the data is installed in the store.
  11. renderAppConfig:...
  12. ssrCacheConfig: is used to transfer the cache. You can leave it untouched