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

@eternal-twin/website

v0.10.3

Published

Eternal-Twin's website

Downloads

54

Readme

Eternal-Twin Web Application

This package contains the Eternal-Twin Web Application. It uses the Angular framework.

The application supports internationalization and both client-side and server-side rendering.

Overview

Sources

All the source files are in the ./src/ directory. This is the only directory you should edit manually.

The directory ./src/main/ contains the top-level server code. It is compiled as native ESM to ./main using Typescript. All the other directories in ./src/ are handled by Angular's CLI and bundled using webpack and compiled to ./app/. Relative imports in ./src/main/ must use the .js extension, relative imports in the other directories must be extensionless.

When there are pairs of files with the .server.ts and .browser.ts suffixes, it indicates that they both have the same role but one is used for server-side rendering and the other in the browser.

  • ./src/app/: main Angular application directory. It contains Angular components and their logic (including routing).
  • ./src/modules: Angular modules, with services (for example, this is where code interacting with the API is located).
  • ./src/assets: Static assets.
  • ./src/browser: Client-side rendering entry point.
  • ./src/server: Server-side rendering entry point.
  • ./src/environments: Environment configuration files for the web-app.
  • ./src/locales: Translation files.
  • ./src/styles: SCSS style files.
  • ./src/main: Top-level server.

Build artifacts

  • ./app/browser/ contains static files. On the production server they are gzip-compressed and directly served by nginx.
  • ./app/server/ contains server-side rendering files: a main.js and index.html for each locale.
  • ./main/ contains the top-level server. It handles routing for the API and the app routes.

Tasks

The project-level tasks are defined as yarn commands, in the scripts field of package.json.

Here are the main actions:

  • yarn run app:serve:browser: Serve the browser-side rendering code, with live-reloading.
  • yarn run app:serve:server: Serve the browser-side and server-side rendering code, with live-reloading.
  • yarn run start (or simply yarn start): Do a full production build, then run the top-level server.
  • yarn run app:prod:build:optimize: Optimize the static assets (not fully crossplatform: requires the gzip CLI).
  • yarn run app:xi18n: Import source-code changes into the translation files (e.g. when new messages are added).