Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@mintlab/kitchen-sink

Package Overview
Dependencies
Maintainers
5
Versions
32
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@mintlab/kitchen-sink

Mintlab utility functions.

  • 3.5.1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
0
Maintainers
5
Weekly downloads
 
Created
Source

@mintlab/kitchen-sink npm version

Everything but: miscellaneous Mintlab utility functions.

Installation

$ npm install @mintlab/kitchen-sink

Usage

Examples

Public API entry point:

const kitchenSink = require('@mintlab/kitchen-sink');

Destructuring:

const { dictionary } = require('@mintlab/kitchen-sink');

Single module:

const dictionary = require('@mintlab/kitchen-sink/dictionary');

Development

Docker

Start an interactive ash shell for development:

$ docker-compose exec sink sh

If you edit .*rc files in ./root, you must manually copy them to your current working directory in the container.

The package*.json files are symlinked because they can be mutated both on the host and in the container.

Publication

The package is published with semantic-release-gitlab on every merge to the master branch. Mind your commit messages.

Files in ./source are copied to the root and removed after publication. See the prepublishOnly and postpublish lifecycle scripts in package.json.

Manual emergency publication

In edge cases when semantic release cannot increment:

  • if you are not in the container, copy root/.npmrc and root/package.json to the working copy root
  • update the version field in package.json
  • run npm login if needed
  • run npm publish --access public
  • create a matching version tag in gitlab
  • do not commit your changes

Infrastructure

The modules in this package export Node.js modules and work natively on the server. There is no transpilation and distribution build included, to consume them in the browser use your bundler of choice.

See also

Unit testing

Unit tests use tape, a TAP producing test harness for node.

Async

No special libraries or plugins are needed for async tests:

  1. make the test callback async
  2. plan the number of assertions
  3. await the async value
  4. proceed as with any other test
Example
test('The async answer', async assert => {
  assert.plan(1);

  const answer = await new Promise(resolve => {
    setTimeout(() => resolve(42), 1000);
  });

  assert.equal(answer, 42, 'is always 42');
  assert.end();
});

License

Copyright 2017 Mintlab B.V.

Licensed under the EUPL, Version 1.1 or – as soon they will be approved by the European Commission - subsequent versions of the EUPL (the "Licence").

You may not use this work except in compliance with the Licence.

You may obtain a copy of the Licence at: https://joinup.ec.europa.eu/software/page/eupl

FAQs

Package last updated on 06 Sep 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc