open-index/open-npm huggingface dataset:
npm package: @oasisdex/summer-cli
Description: A cli that will bring us one step closer to nirvana. 🙏
Author: Summer.di devs
Latest version: 0.0.0

oclif-hello-world
=================

oclif example Hello World CLI

[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![CircleCI](https://circleci.com/gh/oclif/hello-world/tree/main.svg?style=shield)](https://circleci.com/gh/oclif/hello-world/tree/main)
[![GitHub license](https://img.shields.io/github/license/oclif/hello-world)](https://github.com/oclif/hello-world/blob/main/LICENSE)

<!-- toc -->
* [Usage](#usage)
* [Commands](#commands)
<!-- tocstop -->
# Usage
<!-- usage -->
```sh-session
$ npm install -g @oasisdex/summer-cli
$ summer-cli COMMAND
running command...
$ summer-cli (--version)
@oasisdex/summer-cli/0.0.0 darwin-arm64 node-v18.16.0
$ summer-cli --help [COMMAND]
USAGE
  $ summer-cli COMMAND
...
```
<!-- usagestop -->
# Commands
<!-- commands -->
* [`summer-cli conf [KEY] [VALUE]`](#summer-cli-conf-key-value)
* [`summer-cli get-token [WALLET] TOKEN`](#summer-cli-get-token-wallet-token)
* [`summer-cli help [COMMANDS]`](#summer-cli-help-commands)
* [`summer-cli setup`](#summer-cli-setup)

## `summer-cli conf [KEY] [VALUE]`

manage configuration

```
USAGE
  $ summer-cli conf [KEY] [VALUE] [-h] [-k <value>] [-v <value>] [-d] [-p <value>] [-n <value>] [-d
    <value>]

ARGUMENTS
  KEY    key of the config
  VALUE  value of the config

FLAGS
  -d, --cwd=<value>      config file location
  -d, --delete           delete?
  -h, --help             show CLI help
  -k, --key=<value>      key of the config
  -n, --name=<value>     config file name
  -p, --project=<value>  project name
  -v, --value=<value>    value of the config

DESCRIPTION
  manage configuration
```

_See code: [conf-cli](https://github.com/natzcam/conf-cli/blob/v0.1.9/src/commands/conf.ts)_

## `summer-cli get-token [WALLET] TOKEN`

Get ERC20 token to given addreess

```
USAGE
  $ summer-cli get-token [WALLET] TOKEN

ARGUMENTS
  WALLET  Wallet address to get token
  TOKEN   (WETH|DAI|USDC|WBTC|STETH|AAVE|UNI|LINK) Token to get

DESCRIPTION
  Get ERC20 token to given addreess

EXAMPLES
  $ summer-cli get-token
```

_See code: [src/commands/get-token.ts](https://github.com/OasisDEX/oasis-earn-sc/blob/v0.0.0/src/commands/get-token.ts)_

## `summer-cli help [COMMANDS]`

Display help for summer-cli.

```
USAGE
  $ summer-cli help [COMMANDS] [-n]

ARGUMENTS
  COMMANDS  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for summer-cli.
```

_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v5.2.20/src/commands/help.ts)_

## `summer-cli setup`

Initial setup of the cli

```
USAGE
  $ summer-cli setup

DESCRIPTION
  Initial setup of the cli

EXAMPLES
  $ summer-cli setup
```

_See code: [src/commands/setup.ts](https://github.com/OasisDEX/oasis-earn-sc/blob/v0.0.0/src/commands/setup.ts)_
<!-- commandsstop -->
npm package: @oasisdigital/atlassian-connect-angular
Description: This package contains the Angular code needed to integrate your Angular application with Atlassian Connect's APIs and global JS system. This package is typically automatically added & used in tangent with the [`@oasisdigital/atlassian-connect-nx-plugin`](
Author: Zachary Kipping
Latest version: 0.1.6

# Atlassian Connect Angular

This package contains the Angular code needed to integrate your Angular application with Atlassian Connect's APIs and global JS system. This package is typically automatically added & used in tangent with the [`@oasisdigital/atlassian-connect-nx-plugin`](https://www.npmjs.com/package/@oasisdigital/atlassian-connect-nx-plugin) npm package.

## Standalone usage

If you are not using this package in tangent with the above nx plugin, you will want to have added the following script your Angular application's `index.html` before making use of the code from this package:

`<script src="https://connect-cdn.atl-paas.net/all.js" type="text/javascript" async></script>`
npm package: @oasisdigital/atlassian-connect-nx-plugin
Description: To install ngrok (which we use as a tunnel for Atlassian Connect to see your localhost app) run one of the following commands:
Author: Zachary Kipping
Latest version: 0.1.6

# Atlassian Connect Nx Plugin

## Prerequisites

### Ngrok

To install ngrok (which we use as a tunnel for Atlassian Connect to see your localhost app) run one of the following commands:

`npm install -g ngrok`

`yarn global add ngrok`

[Once you have installed `ngrok` globally on your device, follow "Step 3" from the `ngrok` documentation to authenticate ngrok for your device.](https://ngrok.com/docs/getting-started/#step-3-connect-your-agent-to-your-ngrok-account)

> In the future we will try to incorporate this authentication into this package to avoid globally installing `ngrok`.

## Installation

Run one of the following commands in a Nx workspace:

`npm install --save-dev @oasisdigital/atlassian-connect-nx-plugin`

`yarn add --dev @oasisdigital/atlassian-connect-nx-plugin`

## Generating Your Atlassian Connect Application

1. Run the following command to create your own Angular + Express applications to run on Atlassian Connect:  
   `npx nx generate @oasisdigital/atlassian-connect-nx-plugin:app`

2. Once you have generated your application you will need to fill out our Atlassian environment configuration. You can do this by copying the `.env.atlassian-connect.template` that was generated in your Angular application and renaming it to `.env.atlassian-connect`. Make sure to fill out the env variables in this file to match your Atlassian configuration!

## Serving Your Application

Run the following command to serve your Angular + Express applications:

`npx nx connect-serve {angular-app-name}`

Replacing the `{angular-app-name}` with the name of your generated Angular application.

> This also includes a `ngrok` tunnel for your convenience.

## Building Your Application

Run the following command to build your Angular + Express applications:

`npx nx connect-build {angular-app-name}`

Replacing the `{angular-app-name}` with the name of your generated Angular application.

> The built files will be under the `dist` directory of your Express application's name.
npm package: @oasisdigital/live-server
Description: simple development http server with live reload capability - fork with no-css-inject
Author: Tapio Vierros
Latest version: 1.3.3

# Live Server Oasis Digital Fork

This is a fork of live-server, hopefully temporary, to add a "no CSS inject" feature very useful during our Angular Boot Camp class:

https://angularbootcamp.com/

# Installation

```
npm install -D @oasisdigital/live-server
```

# Settings

Things are the same as the upstream package:

https://www.npmjs.com/package/live-server

With one new addition:

* `--no-css-inject` - reload page on CSS change, rather than injecting changed CSS


License
-------

Uses MIT licensed code from [Connect](https://github.com/senchalabs/connect/) and  [Roots](https://github.com/jenius/roots).

(MIT License)

Copyright (c) 2012 Tapio Vierros

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
npm package: @oasisdigital/ng-doc-portal
Description: Documentation portal system written natively in Angular
Author: Zachary Kipping
Latest version: 1.9.3

# NgDocPortal

The `@oasisdigital/ng-doc-portal` package allows you to create your own component documentation portal natively in Angular. This system makes use of the latest features of Angular (stand-alone components and lazy loading components) to provide an ergonomic development experience for documenting your angular components. Everything is built natively in angular so there are no hoops to jump through or different libraries/frameworks/syntaxes to learn!

This package is meant to be used in tangent with the `@oasisdigital/ng-doc-portal-plugin` package inside of an Nx Workspace.

Please reference the [ng-doc-portal-plugin](https://www.npmjs.com/package/@oasisdigital/ng-doc-portal-plugin) package to see the full getting started guide.

## Installation

### npm

`npm install --save @oasisdigital/ng-doc-portal`

### yarn

`yarn add @oasisdigital/ng-doc-portal`
npm package: @oasisdigital/rollup-plugin-node-resolve
Description: Bundle third-party dependencies in node_modules. Fork to add es2015-in-es2015 support.
Author: Rich Harris
Latest version: 2.0.2

# rollup-plugin-node-resolve

*This plugin used to be called rollup-plugin-npm*

Locate modules using the [Node resolution algorithm](https://nodejs.org/api/modules.html#modules_all_together), for using third party modules in `node_modules`

# Fork Alert!

This is a (hopefully temporary) published fork, with the new es2015 option shown
below. Hopefully this functionality (as in this fork, or better) will arrive in
the upstream `rollup-plugin-node-resolve` shortly.

## Installation

```bash
npm install --save-dev @oasisdigital/rollup-plugin-node-resolve
```

## Usage

```js
import { rollup } from 'rollup';
import nodeResolve from '@oasisdigital/rollup-plugin-node-resolve';

rollup({
  entry: 'main.js',
  plugins: [
    nodeResolve({
      // use "es2015" field for ES2015 modules with ES2015 code,
	  // if possible
      es2015: true, // Default: false

      // use "module" field for ES2015 modules with ES5 code,
	  // if possible
      module: true, // Default: true

      // use "jsnext:main" if possible
      // – see https://github.com/rollup/rollup/wiki/jsnext:main
      jsnext: true,  // Default: false

      // use "main" field or index.js, even if it's not an ES6 module
      // (needs to be converted from CommonJS to ES6
      // – see https://github.com/rollup/rollup-plugin-commonjs
      main: true,  // Default: true

      // if there's something your bundle requires that you DON'T
      // want to include, add it to 'skip'. Local and relative imports
      // can be skipped by giving the full filepath. E.g.,
      // `path.resolve('src/relative-dependency.js')`
      skip: [ 'some-big-dependency' ],  // Default: []

      // some package.json files have a `browser` field which
      // specifies alternative files to load for people bundling
      // for the browser. If that's you, use this option, otherwise
      // pkg.browser will be ignored
      browser: true,  // Default: false

      // not all files you want to resolve are .js files
      extensions: [ '.js', '.json' ],  // Default: ['.js']

      // whether to prefer built-in modules (e.g. `fs`, `path`) or
      // local ones with the same names
      preferBuiltins: false  // Default: true
    })
  ]
}).then( bundle => bundle.write({ dest: 'bundle.js', format: 'iife' }) );

// alongside rollup-plugin-commonjs, for using non-ES6 third party modules
import commonjs from 'rollup-plugin-commonjs';

rollup({
  entry: 'main.js',
  plugins: [
    nodeResolve({ jsnext: true, main: true }),
    commonjs()
  ]
}).then(bundle => bundle.write({
  dest: 'bundle.js',
  moduleName: 'MyModule',
  format: 'iife'
})).catch(err => console.log(err.stack));
```


## License

MIT