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

@v4fire/core

v3.99.0

Published

V4Fire core library

Downloads

856

Readme

V4Fire Core Library

npm version build status

Coverage Status

This library provides a bunch of isomorphic modules and configurations to work as a foundation for another V4 libraries and contents many base classes and structures, such as queue, persistent key-value storage, subclasses to work with promises, etc.

GitHub

Using as a node.js library

// Register Prelude in the top level of your project
require('@v4fire/core');

const {watch} = require('@v4fire/core/lib/core/object/watch').default;

const {proxy} = watch({a: 1}, console.log);

proxy.a++;

Also, you can require modules by using import.

// Register Prelude in the top level of your project
import '@v4fire/core';

import watch from '@v4fire/core/lib/core/object/watch/index.js';

const {proxy} = watch({a: 1}, console.log);

proxy.a++;

Prepare to build and develop

At first, you should install dependencies using npm:

npm ci

After this you should compile a configuration for TypeScript:

npx gulp build:tsconfig

Configuration and building

All build config files are placed within the config folder. File names of config files are tied with a value of the NODE_ENV environment variable. Build scripts, such as Gulp or Webpack, are contained within the build folder.

To build your project, you should run the following script:

npm run build

Run tests

Before running tests, your project should be built. There are several scripts that run tests:

// runs tests that check typing
npm run test:typescript

// runs tests that check code quality
npm run test:eslint

// runs both previous tests
npm run test:linters

// runs unit tests
npm run test:jasmine

// runs all tests
npm test

Unit tests developing

During test development, it's convenient when the project is rebuilt automatically after changes in code. For this purpose, you can use the following script:

npm run dev

Then you can run tests that you are currently developing:

npx jasmine ./dist/server/path/to/*.spec.js