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

pon-shared-pon.universe.frontend.shared.componentlibrary

v1.0.0

Published

shared components for Pon Universe

Downloads

12

Readme

Prerequisites

! It is expected that you open the Bash terminal in the root of the project. e.g. In Visual Studio Code the terminal is opened with shortcut ctrl + ~

e.g. D:\web\Pon.Universe\Frontend.Shared.ComponentLibrary

  1. Install NVM and restart your computer.

    • Windows: https://github.com/coreybutler/nvm-windows/releases. Download 'nvm-setup.zip'.
    • Linux: See 'Installation' section of Node Version Manager.
  2. Use NVM to install and set the correct version of Node.js. This should be the LTS version.

    Windows:

    • Get [version] by checking the content of the .nvmrc file for the correct Node.js version.
    • Install that Node.js version by executing $ nvm install [version]
    • Set the correct NVM version by executing $ nvm use [version]

    ! Nvm for windows it is not possible to automatically read the .nvmrc file to set the correct version. So manually use the version of the .nvmrc.

    Linux:

    • Run nvm use to set the correct version of Node.js.

Installation

! It is expected that you open the Bash terminal in the root of the project. e.g. In Visual Studio Code the terminal is opened with shortcut ctrl + ~

e.g. D:\web\Pon.Universe\Frontend.Shared.ComponentLibrary node -v

  1. Install the NPM packages by running the following command:
npm install
  1. Link local packages together and install remaining package dependencies
lerna bootstrap

Commands

Publishes the components to the valtech nexus server: https://nexus.valtech.nl/repository/Pon.Universe.Frontend.Shared/

npm run publish

This command will first check the current git branch and state. Publishing is only allowed from the develop branch and the branch must be up-to-date with no uncommited changes. If those criteria are not met, the command will throw an exception and the publication will not continue.

Lints and fixes files

npm run lint

Run your unit tests

npm run test:unit

More information on creating / deleting packages and adding dependencies to packages:

https://efocus.atlassian.net/wiki/spaces/PONUNI/pages/1237975718/Front-end+Shared+Component+Library

Troubleshooting

Windows:

'npm' is not recognized as an internal or external command

Fix: Update to the latest nvm version and reinstall the used node version. Version 1.1.6 of NVM is incompatible with the later downloads of node and causes an error when installing NPM.


Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 8.x

Fix: npm rebuild node-sass

Tools

For real-time code analysis & formatting in Visual Studio Code:

  1. Install a EditorConfig plugin for your prefered IDE.

    • Visual Studio Code: e.g. EditorConfig for VS Code
  2. Install a PrettierEditor plugin for your prefered IDE.

    • Visual Studio Code: e.g. Prettier - Code formatter

    ! Make sure that you point your Editor to the .prettierignore in the root of the project.

    ! e.g. Visual Studio Code: If you open the editor in the root of the project Pon.Universe/Automotive.Cluster.Common.CarSalesTool you don't need to change anything.

  3. Install a ESLint plugin for your prefered IDE.

    • Visual Studio Code: e.g. ESLint
  4. Install a Vue plugin for your prefered IDE.

    • Visual Studio Code: e.g. Vetur

For real-time code analysis & formatting in the browser:

  1. Install Vue devtools for the browser

Visual Studio Code Settings

How to open the settings.json see here

    "editor.formatOnSave": true,
    "eslint.autoFixOnSave": true,
    "eslint.validate": [
        "javascript",
        "javascriptreact",
        {
            "language": "vue",
            "autoFix": true
        }
    ],