Giter Site home page Giter Site logo

ncats / lsc Goto Github PK

View Code? Open in Web Editor NEW
3.0 21.0 8.0 1.88 MB

LabShare Command: CLI interface for LabShare projects

License: MIT License

JavaScript 14.85% HTML 3.58% TypeScript 78.45% Dockerfile 0.41% SCSS 2.70% Shell 0.02%
configuration cli winston-logger yargs

lsc's Introduction

Coverage Status Build Status codecov

LSC

has all the code for CLI of LabShare. It is based on flatIron.

Install

npm i -g @labshare/lsc

Usage

Run lsc help to display a list of available commands.

App Templates

Run lsc create app to display a list of available templates.

  • api: API template powered by LoopBack and LabShare Services
  • ui: UI template powered by Angular and LabShare Services
  • cli: CLI template LabShare Services

You can also provide CLI arguments for a programmatic usage:

  • --name my-app-name
  • --description 'some description'
  • --type ui (can be ui, api, or cli)
  • -y (Bypass "continue?" question, useful for automated scripts)

Note: The command will add all the app's files. It is recommended to create a folder and execute the command inside that folder.

lsc Settings

To define the cliPattern and packageDependencies, you can use the lsc property at package.json

  "lsc": {
    "cliPattern": "dist/cli/*.js",
    "packageDependencies":[]
  },

In the example , lsc is reading the package's cli commands from the cliPattern directory, also is checking the packageDependencies from the same section.

Package Dependencies

The add commands from other cli's labShare packages, you will need to specify the packageDependenciesproperty at the package.json file. This property can be defined inside the lsc property or as a root property at the package.json file.

This is an array of all the projects which contains cli commands, for example:

   "packageDependencies": [
    "@labshare/services",
    "@labshare/lsc"
  ],

In the example , lsc is reading the package's cli commands from each module declared at packageDependencies,

Documentation

How to define new CLI commands for LSC

Working with package configuration files [Optional]

Tests

npm test

lsc's People

Contributors

abdul-akibu avatar artemnih avatar dkrantsberg avatar ekdev2 avatar greenkeeper[bot] avatar jamilomar avatar kallev avatar keatsk avatar kv979w avatar rafaelcalpena avatar rsarosh avatar semantic-release-bot avatar snyk-bot avatar suhasys avatar

Stargazers

avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

caok2709 tinatangcs jamilomar lpsstereotip abdul-akibu miki1100 kananlanginhooper niaid

lsc's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of @types/lodash is breaking the build 🚨

Version 4.14.109 of @types/lodash was just published.

Branch Build failing 🚨
Dependency @types/lodash
Current Version 4.14.108
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
  • ❌ coverage/coveralls First build on greenkeeper/@types/lodash-4.14.109 at 84.894% Details
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

npm ERR! peer semantic-release@">=15.0.0 <16.0.0" from @labshare/[email protected]

After lsc create app

Tried running npm install

$ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: thrizer@0.0.0
npm ERR! Found: semantic-release@17.4.2
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"^17.0.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=15.0.0 <16.0.0" from @labshare/[email protected]
npm ERR! node_modules/@labshare/semantic-release-config
npm ERR!   dev @labshare/semantic-release-config@"^1.1.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/appinventiv/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/appinventiv/.npm/_logs/2021-04-19T12_02_10_509Z-debug.log

Platform and dependencies

Nodejs v14.16.1

npm 7.10.0

platform Ubuntu 20.04.2 LTS

An in-range update of untildify is breaking the build 🚨

Version 3.0.3 of untildify was just published.

Branch Build failing 🚨
Dependency untildify
Current Version 3.0.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

untildify is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
  • ❌ coverage/coveralls First build on greenkeeper/untildify-3.0.3 at 84.894% Details
Commits

The new version differs by 3 commits.

  • 12bfb52 3.0.3
  • dee5c5d Use lookahead expression for cleaner replace (#14)
  • 732f49f Make CI pass again (#15)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

ajv-errors and ajv-keywords

OCT 2021: Setting up with just LSC with an app option creates an error when running npm run start. The error seems to be related with ajv-errors, ajv-keywords, and ajv. Fix for this is to replace any current versions of ajv-errors with v3.0.0 and ajv-keywords with v5.0.0

Sample of the error:

Error: Cannot find module 'ajv/dist/compile/codegen'
Require stack:
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/ajv-keywords/dist/definitions/typeof.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/ajv-keywords/dist/keywords/typeof.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/ajv-keywords/dist/keywords/index.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/ajv-keywords/dist/index.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/node_modules/@loopback/rest/dist/validation/ajv-factory.provider.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/node_modules/@loopback/rest/dist/coercion/coerce-parameter.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/node_modules/@loopback/rest/dist/parser.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/node_modules/@loopback/rest/dist/index.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/dist/src/providers/authentication.provider.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/dist/src/providers/index.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/dist/src/component.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/dist/src/index.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/dist/index.js
- /Users/nikitalysov/Projects/cyto-explorer/api/node_modules/@labshare/services-auth/index.js
- /Users/nikitalysov/Projects/cyto-explorer/api/dist/application.js
- /Users/nikitalysov/Projects/cyto-explorer/api/dist/index.js
- /Users/nikitalysov/Projects/cyto-explorer/api/index.js

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL https://[secure]@github.com/LabShare/lsc.git.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of @types/winston is breaking the build 🚨

Version 2.4.4 of @types/winston was just published.

Branch Build failing 🚨
Dependency @types/winston
Current Version 2.3.9
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

@types/winston is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of inquirer is breaking the build 🚨

Version 6.2.0 of inquirer was just published.

Branch Build failing 🚨
Dependency inquirer
Current Version 6.1.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

inquirer is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/inquirer-6.2.0 at 80.603% (Details).
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

An in-range update of semantic-release is breaking the build 🚨

Version 15.5.4 of semantic-release was just published.

Branch Build failing 🚨
Dependency [semantic-release](https://github.com/semantic-release/semantic-release)
Current Version 15.5.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • ✅ coverage/coveralls First build on greenkeeper/semantic-release-15.5.4 at 86.681% Details
Release Notes v15.5.4

15.5.4 (2018-06-15)

Bug Fixes

  • use git ls-remote to verify if the remote branch is ahead (2b6378f)
Commits

The new version differs by 2 commits.

  • 2b6378f fix: use git ls-remote to verify if the remote branch is ahead
  • 24a8052 refactor: simply EGITNOPERMISSION error parameters

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

An in-range update of glob is breaking the build 🚨

Version 7.1.3 of glob was just published.

Branch Build failing 🚨
Dependency glob
Current Version 7.1.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

glob is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ✅ coverage/coveralls: First build on greenkeeper/glob-7.1.3 at 80.603% (Details).
Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of snyk is breaking the build 🚨

Version 1.81.0 of snyk was just published.

Branch Build failing 🚨
Dependency snyk
Current Version 1.80.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits

The new version differs by 1 commits.

  • 8db3a39 feat: bump nuget plugin to 1.6.1

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of fluent-logger is breaking the build 🚨

Version 2.8.0 of fluent-logger was just published.

Branch Build failing 🚨
Dependency fluent-logger
Current Version 2.7.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

fluent-logger is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 8 commits.

  • c8c5895 2.8.0
  • af2a8b2 Merge pull request #100 from fluent/support-winston-3
  • ec1c4d7 Use HTTPS
  • 31b0b02 Follow winston 3.0.0 API changes
  • 7dc6cae Support Winston 3.0.0
  • b5ca716 Run yarn upgrade
  • 3b4463f Merge pull request #99 from fluent/reset-send-queue-size
  • f7fc121 Subtract _sendQueueSize after flush queue

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL https://[secure]@github.com/LabShare/lsc.git.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL https://[secure]@github.com/LabShare/lsc.git.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of snyk is breaking the build 🚨

Version 1.88.0 of snyk was just published.

Branch Build failing 🚨
Dependency snyk
Current Version 1.87.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • ✅ coverage/coveralls First build on greenkeeper/snyk-1.88.0 at 80.469% Details
Commits

The new version differs by 2 commits.

  • 79a8d6c feat: Improved CLI output to match closer the web UI
  • a46b153 fix: bump docker plugin to 1.10.3

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of gulp-rename is breaking the build 🚨

Version 1.2.3 of gulp-rename was just published.

Branch Build failing 🚨
Dependency gulp-rename
Current Version 1.2.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

gulp-rename is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
  • ❌ coverage/coveralls First build on greenkeeper/gulp-rename-1.2.3 at 84.894% Details
Commits

The new version differs by 20 commits.

  • 239c2b6 exclude package-lock
  • 8d4eecc update deps, 1.2.3
  • 165949e Merge pull request #79 from TheDancingCode/remove-gutil
  • 33e3fa7 Update engines field in package.json
  • 8104e4b Update travis build
  • bb11b80 Make test pass on Windows
  • 457db2e Fix code style error
  • bdfc359 Drop dependency on deprecated gulp-util
  • 3b4fdf8 Merge pull request #72 from lleaff/patch-1
  • fa84ece Fix confusing example
  • 17d44ec Merge pull request #56 from Josiah/clone-original-file
  • ba5ab6d Merge pull request #57 from florianeckerstorfer/patch-1
  • 6cf0627 Return path in rename by function example
  • 5001e08 Test that gulp-rename works for parallel streams
  • fb1a8e3 Clone the original file prior to renaming

There are 20 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.