🚀 Big News:Socket Has Acquired Secure Annex.Learn More →
Socket
Book a DemoSign in
Socket

@gigster/module-loopback-base

Package Overview
Dependencies
Maintainers
7
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@gigster/module-loopback-base

Role | Name | Email | Slack ---- | ---- | ----- | ----- *Product Owner* | Ryan Borker | [borker@gigster.com](mailto:boker@gigster.com) | [@borker] *Maintainer* | Jerome Curlier | [jerome@gigster.com](mailto:jerome@gigster.com) | [@jerome]

latest
npmnpm
Version
1.1.1
Version published
Maintainers
7
Created
Source

loopback_base

RoleNameEmailSlack
Product OwnerRyan Borkerborker@gigster.com[@borker]
MaintainerJerome Curlierjerome@gigster.com[@jerome]

Overview

The Loopback base module modify the Loopback generated boilerplate to add code and configuration to ease further module development, to set the standard for the project and to productionize the Loopback project.

Usage

      modules:
        - name: loopback-base
          location: >-
            https://github.com/liquidlabs-co/gig-modules/tree/master/block/loopback-base

Endpoints

The modules generate the endpoind for the ping:

EndpointDescription
POST /pingProvide {"started":"2017-12-15T22:25:31.416Z","uptime":12.795} for the application to enable monitoring.

Generation

Boot

The following boot file is added to the Loopback application:

  • ping.js

Configuration

The following configuration file is added to the Loopback application:

  • component-config.production.json

Test

The following test files are added to the Loopback application:

  • test\e2e\explorer\index.spec.js
  • test\e2e\ping\index.spec.js

Troubleshooting

Tests

Module tests are defined using a test/scenarios.yaml file. This file defines the set of example gigs that we generate as part of integration testing. To run all tests, run yarn test at the root of this module.

Each scenario is generated in test/scenario/<name> which you can then cd into and run the actual app. For a scenario called default, this is done via:

cd test/scenario/default
yarn install

# Run tests.
yarn test

# Start the app.
yarn start

TODO

FAQs

Package last updated on 19 Jan 2018

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