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

@cfl/bigfoot-search-service

v1.1.0

Published

This generator creates TypeScript/JavaScript client that utilizes [Fetch API](https://fetch.spec.whatwg.org/). The generated Node module can be used in the following environments:

Downloads

2

Readme

TypeScript-Fetch

This generator creates TypeScript/JavaScript client that utilizes Fetch API. The generated Node module can be used in the following environments:

Environment

  • Node.js
  • Webpack
  • Browserify

Language level

  • ES5 - you must have a Promises/A+ library installed
  • ES6

Module system

  • CommonJS
  • ES6 module system

It can be used in both TypeScript and JavaScript. In TypeScript, the definition should be automatically resolved via package.json. (Reference)

Installation

swagger-codegen does not generate JavaScript directly. The generated Node module comes with package.json that bundles typescript and typings so it can self-compile during prepublish stage. The should be run automatically during npm install or npm publish.

CAVEAT: Due to privilege implications, npm would skip all scripts if the user is root. You would need to manually run it with npm run prepublish or run npm install --unsafe-perm.

NPM

You may publish the module to NPM. In this case, you would be able to install the module as any other NPM module. It maybe useful to use scoped packages.

You can also use npm link to link the module. However, this would not modify package.json of the installing project, as such you would need to relink every time you deploy that project.

You can also directly install the module using npm install file_path. If you do npm install file_path --save, NPM will save relative path to package.json. In this case, npm install and npm shrinkwrap may misbehave. You would need to manually edit package.json and replace it with absolute path.

Regardless of which method you deployed your NPM module, the ES6 module syntaxes are as follows:

import * as localName from 'npmName';
import {operationId} from 'npmName';

The CommonJS syntax is as follows:

import localName = require('npmName');

Direct copy/symlink

You may also simply copy or symlink the generated module into a directory under your project. The syntax of this is as follows:

With ES6 module syntax, the following syntaxes are supported:

import * as localName from './symlinkDir';
import {operationId} from './symlinkDir';

The CommonJS syntax is as follows:

import localName = require('./symlinkDir')';