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

plasttic

v2.2.1

Published

Plasttic Web Workflow: A methodology based Front-End development environment.

Downloads

28

Readme

Plasttic

Plasttic Web Workflow

A methodology based Front-End development environment for Static Sites.

npmNPM DownloadsLICENSEVOLTATwitter Follow


About


Welcome! 🖖

Plasttic Web Workflow is a methodology based professional Front-End development environment for Static Sites: HTML and CSS/PostCSS boilerplate, CSS Reset, Atomic Design System, Typescript/Javascript, Dev Server/Build Tool, File structure, Conventions & Best Practices.

This is not a Bundler nor a Framework, though it has some of the features of a Bundler, and it includes tools and rules that will improve the development process and produce quality code, it's built to support a different development process.

This workflow is intended to be open, allowing the developer to adopt or customize the methodology with the objective of producing accessible, scalable and robust interfaces.

Note: The files installed are not empty. The reason is that, by creating a template, it's easier to demonstrate the methodology, concepts and conventions, and even building upon the existing code.

Workflow

Dev Server, Build Tool, File/Folder Structure, HTML Boilerplate, CSS Reset, Templates, Atomic Design CSS, Print CSS, ES Modules, Typescript, PostCSS, CSS Styling, HTML/CSS/JS Minification, Conventions, Linting, Testing, Image Optimization (Soon!)


Related projects


Table of Contents


Methodology


  • Core Fundamentals
  • Best Practices/Conventions
  • Performance/Core Web Vitals
  • Separation of Concerns
  • Documentation
  • Design System/Atomic Design
  • BEM Methodology
  • CSS Reset
  • HTML Boilerplate
  • Semantic HTML/Accessibility
  • Progressive Enhancement
  • CSS/Postcss
  • Typescript/Javascript
  • Code Conventions/Linting
  • Debug/Test

Start


Quick Start

(cd into your projects folder)
npx create-plasttic
cd <project-name>
npm run start
  1. Creates a folder with the project name you defined
  2. Downloads and installs the latest version of Plasttic Web Workflow
  3. Installs all the project dependencies, Git hooks (Linting pre-commit), Playwright install

Typescript


  • npm run start installs Typescript globally *although it is installed as a devDependency, the Dev Scripts may not work as expected if you do not install it globally also.
  • TS-Reset is installed by default. If you wish to disable it, delete the reset.d.ts file.
  • Linting: Prettier ESLint (requires some configuration: see the plugin page and the Plasttic VSCode settings). Install ESLint to provide error and warning messages in the files.

Development


  • Run npm run dev to start the dev server on http://localhost:8000 *

  • Run npm run build when you are ready to publish *

  • *Source folder: src/, Dev folder: dev/, Build folder: dist/

Customizing


(Note: The files installed are not empty. The reason is that, by creating a template, it's easier to demonstrate the methodology, concepts and conventions, and even building upon the existing code.)

  • Search for "TODO:" in comments, relative to info that needs to be changed or checked. After, change it to "DONE:". If using VS Code, use the Todo Tree extension or TODO Highlight
  • If .##gitignore## exists, rename it to .gitignore and customize to your project info.
  • :warning: Do not delete, rename or move files in the root folder. Do not delete, move or rename folders in the src folder, except the templates folder. Do not delete or move the following files in assets folder: js/scripts.ts (you can rename to scripts.js), js/modules/module.ts (at least one file name.ts/.js must exist), css/styles.css and css/print.css (do not rename this CSS files) - this files must exist, even if empty. If not used, delete the corresponding tag in the HTML page. :warning:

Development with https


  • Step 1: Run mkdir certs
  • Step 2: Run cd certs
  • Step 3: Install certificate with mkcert
  • Step 4: Check certificate filenames and/or path in the file browser-sync.cjs
  • Step 5: Run npm run dev:ssl to start the dev server on https://localhost:8000

Libraries


  • TS-Reset (If you wish to disable it, delete the reset.d.ts file.)
  • Zod

Linting


(Extends the editor File Type rules, .editorconfig and VS Code settings)

| | Files * | Usage | Result | Config | Plugin | References | | ------------- | ------------------- | ------------------------------------------ | -------------------------------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Prettier | html, css, md, json | On Save, Build Script, Pre Commit, Plugin | Errors, Warnings and Fix | .prettierrc, .prettierignore | Prettier | | | ESLint | js, ts (src/tests) | On Save, Build Script, Pre Commit, Plugins | Errors, Warnings and Fix | .eslintrc.cjs, .eslintignore | Prettier + ESLint, ESLint ** | Airbnb, Airbnb Typescript, Wes Bos ESLint Setup | | Stylelint | css | On Save, Build Script, Pre Commit, Plugin | Warnings, Limited fixes and CSS sorting | .stylelintrc.json | Stylelint | |

*all linting is done on the src folder, except for ESLint that also lints the tests folder.
**see Typescript

Testing


| | About | Usage | Folders * | Notes | Plugins | | ------------ | ---------------------------- | ---------------------------------------------------- | ---------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | Jest | Unit nad Integration testing | Build tool, Pull Request, Terminal (npx jest) | dev, ci, reports | Typescript support, Jest CLI | Jest | | Playwright | End-to-End testing | Build tool, Pull Request, Terminal | dev, ci, reports | | Playwright Test for VSCode | | Lighthouse | Web Core Vitals | npm run test:vitals:page --page=page.html | reports | | | | Unlighthouse | Lighthouse website testing | npm run test:vitals:site --url=https://example.com | reports ** | | |

*This folders are inside the tests root folder separated by test app. For Jest and Playwright, the tests placed on the ci folder will run automatically on npm run build and on pull request and the dev folder is were individual tests are placed to run from the terminal with npx jest.
**The Unlighthouse reports folder .unlighthouse is located in the root directory.


Manual Install (Clone)

  • Step 1: Copy the repository git clone https://github.com/tojeiro-me/Plasttic.git

  • Step 2: Move the the contents of the package folder into your <project-folder>

  • Step 3: Run cd <project-folder>

  • Step 4: Rename .##gitignore## to .gitignore

  • Step 5: Run npm run start

    • Installs the needed dependencies
    • Installs Husky Git Hooks
    • Initializes Playwright
  • Step 6: Run npm run dev to start the dev server on http://localhost:8000 *

  • Step 7: Run npm run build when you are ready to publish *

  • *Source folder: src/, Dev folder: dev/, Build folder: dist/

Templates


Documentation


  • File Comments
  • Check docs folder :construction:
  • Documentation website (Soon!)

Please check the CHANGELOG for major or breaking changes

Links


  • Website :construction:
  • Documentation (Soon!)

Follow


TwitterMastodonGithub


License



Plasttic