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

idai-field-components

v0.1.0

Published

iDAI.field Components

Downloads

2

Readme

iDAI.components 2

Getting started

Clone this repository and run

npm install
npm run build
npm start (= npm run server)

The last command starts a webserver listening on http://localhost:8083.

Demo

The demo app is used to display the functionality of the library. It makes use of the configuration files at

demo/config

which will get automatically created from their template counterparts by npm run build in case they don't exist.

Testing

Unit test the library files with

$ npm test

E2E test the library by running the server, then opening another terminal and running

$ npm run e2e

Using the library

SCSS files:

src/scss/idai-components-2.scss

Module exports, which can be used via systemjs:

configuration.ts
core.ts
datastore.ts
documents.ts
idai-field-map.ts
idai-field-model.ts
messages.ts
persist.ts
widgets.ts

Publishing via NPM

A npm account (which could be signed up here: https://www.npmjs.com/signup) and the user rights on this npm package are required. To make sure the version number on github is not behind your local version it is recommended to maintain the following order of commands when publishing

git add . && git commit -m ""         # Commit your local changes
npm login
npm run build
npm version patch -m "New release %s" # which creates another commit
npm publish
git push