open-index/open-npm huggingface dataset:
npm package: @opera_build/standard-components
Description: The `manifest.json` file exports the definitions of all components available in this version of the client library. The manifest is used by the builder to correctly display components and their settings, and know how to correctly interact with them.
Latest version: 0.9.126

## Manifest

The `manifest.json` file exports the definitions of all components available in this version
of the client library. The manifest is used by the builder to correctly display components and
their settings, and know how to correctly interact with them.



### Component Definitions

The object key is the name of the component, as exported by `index.js`.

- **name** - the name displayed in the builder
- **description** - not currently used
- **icon** - the icon displayed in the builder
- **hasChildren** - whether the component accepts children or not
- **styleable** - whether the component accepts design props or not
- **dataProvider** - whether the component provides a data context or not
- **bindable** - whether the components provides a bindable value or not
- **settings** - array of settings displayed in the builder

###Settings Definitions

The `type` field in each setting is used by the builder to know which component to use to display
the setting, so it's important that this field is correct. The valid options are:

- **text** - A text field
- **select** - A select dropdown. Accompany these with an `options` field to provide options
- **datasource** - A datasource (e.g. a table or a view)
- **boolean** - A boolean field
- **number** - A numeric text field
- **detailURL** - A URL to a page which displays details about a row.
Exclusively used for grids which link to row details.


The available fields in each setting definition are:

- **type** - the type of field which determines which component the builder will use
to display the setting
- **key** - the key of this setting in the component
- **label** - the label displayed in the builder
- **defaultValue** - the default value of the setting
- **placeholder** - the placeholder for the setting


### Добавление компонента
1. прописать компонент в index.js и manifest.json, в нижнем регистре
2. добавить название компонента в нужную группу в /builder/src/components/design/AppPreview/componentStructure.json, в нижнем регистре
npm package: @operandinc/react
Description: A component library for the Operand products.
Author: Operand Inc.
Latest version: 0.1.3

# Operand React

A component library for the Operand products.

# Component Styling

Currently there is no custom styling for the component and we used TailwindCSS to style the component.

## Non-Tailwind Projects:

We have provided a minified tailwind.css file that can be imported to style the component for non-tailwind projects.

```jsx
import '@operandinc/react/dist/operand.css';
```

## Tailwind Projects:

Projects with tailwind must simply include the node-module in the contents section of ‘tailwind.config.js’.

```jsx
module.exports = {
  content: [
		....
    "./node_modules/@operandinc/react/dist/*.js",
  ],
	....
}
```

# Questions?

Send us a message at [support@operand.ai](mailto:support@operand.ai).
npm package: @operandinc/sdk
Description: The official Typescript SDK for the [Operand](https://beta.operand.ai) API. Read more on our [docs](https://docs.operand.ai).
Author: Operand, Inc.
Latest version: 5.0.23

# Operand SDK

The official Typescript SDK for the [Operand](https://beta.operand.ai) API. Read more on our [docs](https://docs.operand.ai).
npm package: @operanex/ffy-errors
Description: Standard errors for FFY
Author: Yehudi Hollevoet
Latest version: 1.0.2

# FFY Errors
Standard errors for FFY

## Usage

### Install
Install the module on your node server or service via command line
´´´
npm install @operanex/ffy-errors
´´´
Or via yarn
´´´
yarn add @operanex/ffy-errors
´´´

### Generate errors
The errors are used to be handled by Express but could be used by other systems, in order to create an error perform the following
```typescript

import errors from '@operanex/ffy-errors'

const err = errors.notAuthorized(`You do not have access to this API`);
```

### Handle errors in express
```typescript
import { isFFYError, errors } from '@operanex/ffy-errors'

app.use((error: FFYError|Error, req, res, next) => {
  if(isFFYError(error)) {
    res.status(error.httpCode).json({
      message : error.message,
      code: error.code,
      data: error.data 
    })
  } else {
    res.status(500).json(errors.serverError(error))
  }
})
```

## Development

Process of publishing

1) Develop
2) Run your tests `npm test` or `yarn test` 
3) Run lint `npm run lint` or `yarn lint` if there is an issue you can run `npm run lint-fix` or `yarn lint-fix` to fix them.
4) Upgrade your version by running `npm version prepatch`
5) Push your version