open-index/open-npm huggingface dataset:
npm package: @hublo/sails-postgresql
Description: a postgreSQL adapter for Waterline and Sails.js
Author: Cody Stoltman
Latest version: 1.0.0

![image_squidhome@2x.png](http://i.imgur.com/RIvu9.png)

# PostgreSQL Sails/Waterline Adapter

[![Build Status](https://travis-ci.org/balderdashy/sails-postgresql.png?branch=master)](https://travis-ci.org/balderdashy/sails-postgresql) [![NPM version](https://badge.fury.io/js/sails-postgresql.png)](http://badge.fury.io/js/sails-postgresql)

A [Waterline](https://github.com/balderdashy/waterline) adapter for PostgreSQL. May be used in a [Sails](https://github.com/balderdashy/sails) app or anything using Waterline for the ORM.

## Install

Install is through NPM.

```bash
$ npm install sails-postgresql
```

## Configuration

The following config options are available along with their default values:

```javascript
config: {
  database: 'databaseName',
  host: 'localhost',
  user: 'root',
  password: '',
  port: 5432,
  poolSize: 10,
  ssl: false
};
```
Alternatively, you can supply the connection information in URL format:
```javascript
config: {
  url: 'postgres://username:password@hostname:port/database',
  ssl: false
};
```


We are also testing features for future versions of waterline in postgresql. One of these is case sensitive string searching. In order to enable this feature today you can add the following config flag:

```javascript
postgresql: {
  url: 'postgres://username:password@hostname:port/database',
  wlNext: {
    caseSensitive: true
  }
}
```

## Model Level Config

You can use model level config options to specify a `schema` to use. This is done by adding the `meta` key `schemaName`.

```javascript
module.exports = Waterline.Collection.extend({
  tableName: 'user',
  meta: {
    schemaName: 'foo'
  },

  identity: 'user',
  connection: 'myAwesomeConnection',

  attributes: {
    name: 'string'
  }
});
```

## Testing

Test are written with mocha. Integration tests are handled by the [waterline-adapter-tests](https://github.com/balderdashy/waterline-adapter-tests) project, which tests adapter methods against the latest Waterline API.

To run tests:

```bash
$ npm test
```

## About Waterline

Waterline is a new kind of storage and retrieval engine.  It provides a uniform API for accessing stuff from different kinds of databases, protocols, and 3rd party APIs.  That means you write the same code to get users, whether they live in mySQL, LDAP, MongoDB, or Facebook.

To learn more visit the project on GitHub at [Waterline](https://github.com/balderdashy/waterline).
npm package: @hublot-io/define-model
Description: defineModel implementation for vue 2.7 according to 3.4 usage
Author: Alexandre BERTRAND
Latest version: 1.0.1

# defineModel

defineModel implementation for vue 2.7 according to 3.4 usage

### Installation 

```
yarn add @hublot-io/defineModel
```

### Usage

#### Component with single v-model 

When your component only needs to expose a single v-model, you can use it as in Vue 3.4.


```parent.vue 

<template>
    <span>
      <HelloWorld v-model="classic" />
        <br>
        <div>Classic Model : {{ classic  }}</div><br>
    </span>
  </template>
  
  <script lang="ts" setup>

      import { ref } from 'vue';
      import HelloWorld from './components/HelloWorld.vue';

      const classic = ref()

  </script>
```


You only need to add the import of defineModel in the child for it to be found. When you migrate to Vue 3.4, you will simply need to remove the import.


```children.vue 

<template>
  <div>
    <input placeholder="classic" v-model="classic"></input>
  </div>
</template>

<script lang="ts" setup>
import { defineModel } from '@hublot-io/defineModel'

const classic = defineModel<string>()

</script>

```




#### Component with multiple v-model 

As in Vue 3.4, you have the possibility to add multiple v-models on a component. However, since Vue 2 does not allow arguments on the model directive, you will need to use a custom directive: v-models.
Additionally, you will need to bind the refs of your v-models so that the library can access and modify them.


```parent.vue 

<template>
    <span>
      <HelloWorld v-models:multi="multi" v-models:other="other"  />
        <br>
        <div>Multiple Model  : {{ multi }}</div><br>
        <div>Other  : {{ other }}</div><br>
    </span>
  </template>
  
  <script lang="ts" setup>
      import { ref } from 'vue';
      import { bindModels } from '@hublot-io/defineModel'
      import HelloWorld from './components/HelloWorld.vue';

      const classic = ref()
      const multi = ref('test')
      const other = ref()

      bindModels({ multi, other })
  </script>
  
```

In the child component, you can use defineModel in the same way as in Vue 3.4.

```children.vue 

<template>
  <div>
    <input placeholder="multi" v-model="multi"></input>
    <input placeholder="other" v-model="other"></input>
  </div>
</template>

<script lang="ts" setup>
import { defineModel } from '@hublot-io/defineModel'

const multi = defineModel("multi")
const other = defineModel("other")

</script>

```
npm package: @hublot-io/vite-plugin-vue-demi-component-preview
Description: This Vite plugin support `<preview lang="md">` custom block in SFC for preview single Vue component.
Latest version: 1.1.26

# vite-plugin-vue-component-preview

This Vite plugin support `<preview lang="md">` custom block in SFC for preview single Vue component.

To use this with VSCode + Volar, see https://github.com/johnsoncodehk/volar/discussions/1511

## Setup

`vite.config.ts`

```ts
import { defineConfig } from 'vite';
import vue from '@vitejs/plugin-vue';
import preview from 'vite-plugin-vue-component-preview';

export default defineConfig({
	plugins: [
		preview(),
		vue(),
	],
})
```

`main.ts`

```ts
import { createApp } from 'vue';
import App from './App.vue';
import Preview from 'vite-plugin-vue-component-preview/client';

const app = createApp(App);
app.use(Preview);
```

`tsconfig.json` (For IDE and vue-tsc support)

```json
{
  "vueCompilerOptions": {
    "plugins": ["vite-plugin-vue-component-preview/tooling"]
  }
}
```

## Example

```html
<!-- Component part -->
<template>
	<h1>{{ msg }}</h1>
	<button @click="count++">count is: {{ count }}</button>
</template>

<script setup lang="ts">
import { ref } from 'vue'

defineProps<{ msg: string }>()

const count = ref(0)
</script>

<!-- Preview part -->

<preview lang="md">

	# This is preview page of HelloWorld.vue

	## Props

	| Props       | Description    |
	| ----------- | -------------- |
	| msg         | Title message  |

	## Examples

	<script setup>
	const msgs = [
	'Hello Peter',
	'Hello John',
	];
	</script>

	<template v-for="msg in msgs">
		<slot :msg="msg"></slot>
	</template>

	<style>
	body {
		background-color: green;
	}
	</style>

</preview>
```

Example repo: https://github.com/johnsoncodehk/volar-starter (Open http://localhost:3000/__preview/src/components/HelloWorld.vue to see the result.)

### Self-import

When you want to preview the component including `<slot>`, importing the component itself provides the solution as follows:

```html
<template>
	<div>
		<slot></slot>
	</div>
</template>

<preview lang="md">

	<script setup>
	import TestPreview from './TestPreview.vue'	// TestPreview.vue is the name of this file itself.
	const msgs = ['1', '2']
	</script>

	<template v-for="msg in msgs">
		<TestPreview>
			test {{ msg }}
		</TestPreview>
	</template>

</preview>
```

This method relates to [#17](https://github.com/johnsoncodehk/vite-plugin-vue-component-preview/issues/17).

## Sponsors

<p align="center">
	<a href="https://cdn.jsdelivr.net/gh/johnsoncodehk/sponsors/sponsors.svg">
		<img src="https://cdn.jsdelivr.net/gh/johnsoncodehk/sponsors/sponsors.svg"/>
	</a>
</p>

## Credits

- Markdown parser power by https://github.com/antfu/vite-plugin-vue-markdown
npm package: @hubmap/portal-search
Description: portal-search React component
Author: C McCallum
Latest version: 0.0.4

# portal-search
A simple, opinionated wrapper for [Searchkit](http://www.searchkit.co/).

[NPM](https://www.npmjs.com/package/@hubmap/portal-search)

## Usage

The [demo source code](demo/src/index.js) has been commented to explain usage.

## Development

Checkout the project, `cd`, and then:

```
$ npm install
$ npm start
```

The development server will refresh the browser as you edit the code.

- To run all the Travis checks: `./test.sh`
- To run just the unit tests: `npm run test:watch`
npm package: @hubmap/prov-vis
Description: prov-vis React component
Latest version: 0.0.4

# prov-vis
Generic wrapper for [4dn-dcic/react-workflow-viz](https://github.com/4dn-dcic/react-workflow-viz):
- Takes [W3C PROV-JSON](https://www.w3.org/Submission/prov-json/) as input.
- Call-backs for defining node names and on-click details.
- [NPM package](https://www.npmjs.com/package/@hubmap/prov-vis) provides a React component, and a plain JS interface.

[Demo](https://hubmapconsortium.github.io/prov-vis/)

## Development

This repo is bootstrapped with [NWB](https://github.com/insin/nwb/blob/master/docs/guides/ReactComponents.md).

To use the development demo:
```sh
npm install
npm start
```
and then visit `http://localhost:3000/`.

To preview the static demo:
```sh
npm run build
http-server
```
then visit `http://localhost:8080/`.

## Publish

Make a release branch, confirm that tests pass, and run:
```
./publish.sh
```
That will bump the version, create a tag, publish to NPM, and push to GitHub.
npm package: @hubmap/vitessce-image-viewer
Description: High bit depth, high resolution, many channels, low overhead
Author: Ilan Gold
Latest version: 0.3.3

### vitessce-image-viewer ("Viv") [![npm version](https://badge.fury.io/js/%40hubmap%2Fvitessce-image-viewer.svg)](https://badge.fury.io/js/%40hubmap%2Fvitessce-image-viewer)

A viewer for high bit depth, high resolution, multi-channel images using DeckGL
over the hood and WebGL under the hood. To learn more about the "theory" behind
this, look at [this](https://github.com/hubmapconsortium/vitessce-image-viewer/blob/master/docs/IMAGE_RENDERING.md).

### Build

To build the component alone via `webpack` use `npm run-script build-component`.
To build the demo used for visual testing (seen on `npm start`), run
`npm run-script build-site`.

### Publish

To bump the version number, clean up/update the CHANGELOG.md, and push the tag to Github,
please run `npm version [major | minor | patch]` depending on which you want. Then run `./publish.sh` to publish the package/demo.

### Development

Please install the [Prettier plug-in](https://prettier.io/docs/en/editors.html)
for your preferred editor. (Badly formatted code will fail on Travis.)

For the demo, run `npm start` and you will be able to update the component and use the
`demo/src/App.js` to visually test.

HTTP is acceptable but potentially slower than HTTP2. Our demo uses Google Cloud Storage, which is HTTP2 by default.

Due to [difficulties](https://github.com/hubmapconsortium/vitessce-image-viewer/issues/103) around compiling shaders on Travis, unit tests and layer lifecycle
tests are run locally as a pre-push hook. Travis runs a test build, linting, and prettier.

### Browser Support

We support both WebGL1 and WebGL2 contexts, which should give near universal coverage. Please file an issue if you find a browser in which we don't work.

### Documentation

Please navigate to [viv.vitessce.io/docs](http://viv.vitessce.io/docs) to see full documenation.
npm package: @hubot-friends/hubot-irc
Description: IRC Adapter for Hubot > version `11`.
Author: Joey Guerra
Latest version: 2.0.2

# hubot-irc (compiled to JS from https://github.com/nandub/hubot-irc)

IRC Adapter for Hubot > version `9`.

# Trying it out

You can try this adapter out by cloning this repo, installing modules and starting the app. If you visit [Freenode](https://webchat.freenode.net) and connect to `#myhubot` and then execute the following commands:

```sh
npm i
npm start
```

You can send a message to `@irc-hubot helo` and it will reply.

# Submitting a PR

We're using `semantic-release` to cut releases from Git commit messages. If you submit a pull request, please make sure to prefix the commit messages with:

- `chore` - no release is cut (e.g. chore: Update build pipeline)
- `fix` - minor version release cut (e.g. fix: Reorder precedence of setting bot name from environment variable)
- `feat` - major version release cut (e.g. feat: some fantastic new feature)
- `BREAKING CHANGE` - if the changes break the public API, in addition to `feat`, add a message for BREAKING CHANGES
    ```
    feat: new feature
    BREAKING CHANGE: Public API was changed from v1 to v2
    ```
npm package: @hubot-friends/hubot-redis-brain
Description: A hubot script to persist hubot's brain using redis Hash Tables
Author: Joey Guerra
Latest version: 4.0.1

![Build and Test Status](https://github.com/hubot-friends/hubot-redis-brain/actions/workflows/ci-pipeline.yml/badge.svg)

# hubot-redis-brain

A hubot script to persist hubot's brain using Redis. This version is fork from the original [hubot-redis-brain](https://github.com/hubotio/hubot-redis-brain) that manages data via a JSON document.

This version utilizes Redis' Hash data structure to manage the data.

See [`scripts/RedisBrain.js`](scripts/RedisBrain.js) for full documentation.

## Installation

In hubot project repo, run:

`npm install @hubot-friends/hubot-redis-brain --save`

Then add **hubot-redis-brain** to your `external-scripts.json`:

```json
[
  "@hubot-friends/hubot-redis-brain"
]
```

## Configuration

`hubot-redis-brain` requires a Redis server to work. It uses the `REDIS_URL` environment variable for determining
where to connect to. The default is on localhost, port 6379 (ie the redis default).

Note: you can use the following command to start a local instance of Redis using Docker:

```sh
docker run --rm -p 6379:6379 -d --name hubot-redis -v $(pwd)/redis-data:/data redis redis-server --appendonly yes"
```

The following attributes can be set using the `REDIS_URL`

* authentication
* hostname
* port
* key prefix

For example, `export REDIS_URL=redis://:password@192.168.0.1:16379/prefix` would
authenticate with `password`, connecting to `192.168.0.1` on port `16379`, and store
data using the `prefix:storage` key.

For a UNIX domain socket, `export REDIS_URL=redis://:password@/var/run/redis.sock?prefix` would authenticate with `password`, connecting to `/var/run/redis.sock`, and store data using the `prefix:storage` key.

### Installing your own

If you need to install and
run your own, most package managers have a package for redis:

* Mac OS X with homebrew: `brew install redis`
* Ubuntu/Debian with apt: `apt-get install redis-server`
* Compile from source: http://redis.io/topics/quickstart

### Redis Twemproxy

If you are using [Twemproxy](https://github.com/twitter/twemproxy) to cluster redis,
you need to turn off the redis ready check which uses the unsupported INFO cmd.

`REDIS_NO_CHECK = 1`