open-index/open-npm huggingface dataset:
npm package: @resolve_ch/file-viewer
Description: A rewrite of react-file-viewer
Latest version: 0.1.5

# file-viewer

Supported file formats:
- bmp
- csv
- docx
- gif
- jpeg
- jpg
- pdf
- png
- xlsx

## Install
```
# via npm
npm install @resolve_ch/file-viewer
```
## FileViewer example
```
import React from 'react';
import ReactDOM from 'react-dom';
import FileViewer from '@resolve_ch/file-viewer';

class App extends React.Component {
  render() {
    return (
      <FileViewer
        filePath="https://upload.wikimedia.org/wikipedia/en/a/a9/Example.jpg"
      </FileViewer>
    );
  }
}

ReactDOM.render(<App/>, document.body);
```
## FileViewer props
```
{
  // The url of the resource to be shown by the FileViewer.
  filePath: string,
  
  // Type of resource to be shown (one of the supported file formats, eg 'png').
  // Passing in an unsupported file type will result in displaying an unsupported file type message (or a custom component).
  // By default, the extension of the filePath is used to determine the fileType, but it can be overwritten using this prop.
  fileType: string [optional]
  
  // Can be used to extend the file-viwer or overwrite the existing drivers,
  // format: '{ [key: string]: React.Component<props: { filePath: string, fileType: string }> }'
  // eg: '{ mp4: VideoPlayerViewer }'
  drivers: object [optional]

  // Called when an error is thrown due to fetching or rendering problems
  onError: function<error: Error, errorInfo: React.ErrorInfo> [optional]
  
  // A component to render in case the file format is not supported.
  UnsupportedComponent: ReactElement<props: { filePath: string, fileType: string }> [optional]
  
  // A component to render in case an error is thrown
  ErrorComponent: ReactElement<props: { error: Error }> [optional]
}
```
## Local development
There is a demo app built into this library that can be used for development purposes.
```
npm run dev
```

## Publish a new version

Log in to npm if not already done with `npm login`, your account needs to be on the `@resolve_ch` org.

* `npm run build`
* `npm publish`
npm package: @resolvejs/babel
Description: > TODO: description
Author: Kamalakar Gadireddy
Latest version: 0.0.11-alpha.0

# @resolvejs/babel

Wrapper `CLI` for babel with support of `config-up` and `@resolve/core`

## Usage

### CLI

```bash
# An wrapper on bable which support config-up to look-up the config
babelc
```

```bash
# An wrapper on bable with `@resolve/core` to resolve and load es modules
node-babel
```
npm package: @resolvejs/config-up
Description: > TODO: description
Author: Kamalakar Gadireddy
Latest version: 0.0.11-alpha.0

# @resolvejs/config-up

CLI Utility/Library to help look-up for a configuration file recursively up till the `node_modules` where config-up is installed.

>**NOTE** This is help-full for mon-repo packages where you can manage one config for across all workspaces

## Usage

### CLI / NPM Script

#### Known CLI's / Commands

```bash
config-up jest --verbose --color
# Will run - jest --verbose --color --config where/the/config/was/found/jest-config.js
```

#### Custom Look-up / Unknown Commands

```bash
config-up --config-name=config --config-ext=js command --config $CONFIG_AT
# Will run - command --config where/the/config/was/found/jest-config.js

config-up --config-name=config --config-ext=js --config-ext=json command --config $config_up_config

# Will run - command --config where/the/config/was/found/jest-config.js
```
npm package: @resolving/angular-pdf-viewer
Description: An AngularJS directive to display PDFs
Author: Varun Vachhar
Latest version: 0.2.9

## Angular PDF Viewer

[![npm-version](https://img.shields.io/npm/v/@resolving/angular-pdf-viewer.svg?color=blueviolet&style=flat-square)](https://www.npmjs.com/package/@resolving/angular-pdf-viewer)

Fork of https://github.com/winkerVSbecks/angular-pdf-viewer, npm package for webpack.

An AngularJS directive to display PDFs. [DEMO](http://codepen.io/winkerVSbecks/full/50010e383d0f80deab97858571400d86/)

## Dependencies

1. [AngularJS](http://angularjs.org/)


## Usage

1. Add as dependency
   - `npm install @resolving/angular-pdf-viewer` 
   - `yarn add @resolving/angular-pdf-viewer` 
2. Ensure AngularJS peer dependency is met
3. Import in client

```js
import '@resolving/angular-pdf-viewer'
```

3. Include the lib as a dependency in your angular app:

```js
var app = angular.module('app', ['pdf']);
```


## Directive

The URL, request headers, scale and delegate-handle can be set using the attributes:

```html
<pdf-viewer
    delegate-handle="my-pdf-container"
    url="pdfUrl"
    scale="1"
    show-toolbar="true"
    headers="{ 'x-you-know-whats-awesome': 'EVERYTHING' }"></pdf-viewer>
```


## Delegate Service (pdfDelegate)

The pdfDelegate service allows you to access and control individual instances of a directive. This allows us to have multiple instances of the same directive in the same controller.

Inject the `pdfDelegate` service into your controller. You can then fetch an instance using it's delegate handle and call methods on it:

```js
pdfDelegate.$getByHandle('my-pdf-container').zoomIn();
```

The following methods are available to the delegate:
- prev
- next
- zoomIn(amount) *default amount = 0.2*
- zoomOut(amount) *default amount = 0.2*
- zoomTo(amount)
- rotate *(clockwise by 90 degrees)*
- getPageCount
- getCurrentPage
- goToPage(pageNumber)
- load


## Change the PDF File

In order to replace the active PDF with another one, you can call the `load` method of the delegate. For example:

```js
pdfDelegate
    .$getByHandle('my-pdf-container')
    .load('url-of-the-new-file.pdf');
```


## Development & Example

- Install: `yarn install`
- Start development server: `yarn start`
- Visit app: `http://localhost:8080`


## Toolbar

The default toolbar can be shown or hidden using the `show-toolbar` attribute. Since the PDF can be easily controlled using the delegate service it's quite trivial to build a custom toolbar. Or place the toolbar on a separate scope.


## Similar projects

1. [angularjs-pdf](https://github.com/sayanee/angularjs-pdf)
2. [ng-pdfviewer](https://github.com/akrennmair/ng-pdfviewer)


## Credit

PDF examples used are [Relativity: The Special and General Theory by Albert Einstein](http://www.gutenberg.org/ebooks/30155) as kindly organized and made available free by [Project Gutenberg](http://www.gutenberg.org/wiki/Main_Page). And the [This is Material Design](http://static.googleusercontent.com/media/www.google.com/en//design/material-design.pdf) by Google.
npm package: @resolvr/core
Description: ## To run
Latest version: 0.0.13

# Resolvr Core

## To run 

Ensure that your CoreNLP is running with the command:

```
java -mx4g -cp "*" edu.stanforp.pipeline.StanfordCoreNLPServer -port 9000 -timeout 15000
```

Run the server with:

```
node index.js
```
npm package: @resolvr/query-engine
Description: Load sequelize models from DB and expose a query engine
Author: Samuel Attard
Latest version: 0.0.10

# Resolvr Query Engine

> The Query Engine connects to your database, turns it into sequelize models, and then runs a query that was outputted from `@resolvr/code`

## Usage

```js
const getQueryEngineFromDB = require('@resolvr/query-engine');

getQueryEngineFromDB({
  host: 'localhost',
  port: 3306,
  type: 'mysql',
  database: 'database_name',
  username: 'user',
  password: 'pass'
}).then((queryEngine) => {
  // This returns an object of table tables and their columns
  // queryEngine.getStructure()

  // Run the actual query
  // queryEngine.query(queryFromCore)
})
```
npm package: @resolvr/results-engine
Description: Parses the output of core and the query-engine into a frontend ready format
Author: Samuel Attard
Latest version: 0.0.4

# Resolvr Results Engine

> The Results Engine parses the output of core and the query-engine into a frontend ready format

## Usage

```js
const { ResultsEngine, ReturnType } = require('@resolvr/results-engine');

const engine = new ResultsEngine();
const type = new ReturnType(
  ReturnType.TYPES.LIST,
  null,
  {
    parseResults: {} // Parsing from core
  }
);
// queryResults is the array returned from the Query Engine
const json = engine.make(type, queryResults);

// json can now be sent back to the front end
```
npm package: @resolvr/transaction-server
Description: Transaction server that handles textual queries to resolver
Author: Samuel Attard
Latest version: 0.0.3

# Resolvr Transaction Server

This is the Transaction Server that manages textual queries

## To use

```js
const server = require('@resolvr/transaction-server');

server.on('new-transaction', (transaction) => {
  transaction.on('request', (requestId, details) => {
    transaction.respond(requestId, { thing: true });
  });
});
server.start();
```
npm package: @resonai/vera-sdk
Description: Vera SDK library
Author: Oren Cohen
Latest version: 0.0.13

# Resonai / Vera SDK

[![NPM Package][npm]][npm-url]
[![NPM Downloads][npm-downloads]][npmtrends-url]

#### Vera SDK library

This SDK allows creation of AR experiences based on JavaScript to run in Vera by Resonai.

### Usage

This code requests `appConfig` and `querySemanticObjects` to get details about
semantic objects currently is use.
Then it creates a scene and a gltf mesh based on the queried data, and it adds
the mesh to the scene.

```javascript
import { veraApi } from '@resonai/vera-sdk'

veraApi.loaded()

const sceneID = 'helloWorldScene'

const appConfig = await veraApi.getAppConfig()
const place = appConfig.Place
const gltf = appConfig['Model URL']

const semanticObjectsDict = await veraApi.querySemanticObjects({
  confKey: appConfig._id,
  fields: ['id,type,name,key,argeometry{center_x,center_y,center_z}']
})
const semanticObject = semanticObjectsDict[place.key]
const geometry = semanticObject['ar:geometry']
const position = [geometry.center_x, geometry.center_y, geometry.center_z]
const meshObj = {
  sceneID,
  id: place._id,
  position,
  gltf
}

await veraApi.initScene({ sceneID })
await veraApi.mesh(meshObj)

```

Additional samples are available at https://github.com/resonai/com.resonai.hello-vera-js

### Change log

N/A


[npm]: https://img.shields.io/npm/v/@resonai/vera-sdk
[npm-url]: https://www.npmjs.com/package/@resonai/vera-sdk
[npm-downloads]: https://img.shields.io/npm/dw/@resonai/vera-sdk
[npmtrends-url]: https://www.npmtrends.com/@resonai/vera-sdk
npm package: @resonance-run/i18next-resonance-plugin
Description: i18next plugin for Resonance
Latest version: 0.4.0

# `@resonance-run/i18next-resonance-plugin`

This package is used for getting Resonance working with i18next.

## Installation

```bash
$ npm install @resonance-run/i18next-resonance-plugin
```

or

```bash
$ yarn add @resonance-run/i18next-resonance-plugin
```

## Usage

```js
import { createInstance } from 'i18next';
import { ResonancePostProcessor } from 'i18next-resonance-plugin';

export function handleRequst(request: Request) {

  // ... clipped for brevity

  const instance = createInstance();
  await instance
    .use(initReactI18next)                        // This example uses react-i18next
    .use(FsBackend)                               // with a filesystem backend

                                                  // `use` the resonance plugin
    .use(new ResonancePostProcessor({ request })) // Make sure to pass in the `request` object
    .init({
      ...i18n,      // spread the configuration
      lng, // The locale we detected above
      ns, // The namespaces the routes about to render wants to use
      backend: { loadPath: resolve('./public/locales/{{lng}}/{{ns}}.json') },
      postProcess: ['resonancePostProcessor'],
    });
}
```