open-index/open-npm huggingface dataset:
npm package: @globalfishingwatch/linting
Description: linting config ready to be used in every gfw frontend project
Author: Satellite Studio
Latest version: 3.1.4

# @globalfishingwatch/linting

[![npm version](https://badge.fury.io/js/%40satellitestudio%2Feslint-config.svg)](https://badge.fury.io/js/%40satellitestudio%2Feslint-config)
[![GitHub license](https://img.shields.io/github/license/satellitestudio/eslint-config.svg)](https://github.com/satellitestudio/eslint-config/blob/master/LICENCE)

Monorepo eslint config with some custom rules and prettier integration

## Installation

```sh
npx install-peerdeps --dev @globalfishingwatch/linting

# or
yarn add @globalfishingwatch/linting -D --peer
```

## Usage

### Eslint

Flat config >= v9

to your `eslint.config.mjs`:

```js
import gfwConfig from '@globalfishingwatch/linting'

export default gfwConfig
```

Legacy usage < v9

1. Add to your `.eslintrc`:

```json
{
  "extends": "@globalfishingwatch/linting/legacy"
}
```

2. Add the config to either your `package.json`:

#### JS

```json
{
  "eslintConfig": {
    "extends": "@globalfishingwatch/linting"
  }
}
```

### Prettier

to your `.prettierrc.js`:

```js
export default '@globalfishingwatch/linting/prettier'
```

## Recommendations

### VS Code

Install the ESLint and Prettier VSCode extensions:

```js
ext install esbenp.prettier-vscode dbaeumer.vscode-eslint
```

Copy this to `settings.json`

```json
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": false, // avoids running the format twice,
  "eslint.autoFixOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  },
```

## LICENCE

[MIT](LICENCE)
npm package: @globalfishingwatch/loaders.gl-fourwings
Description: Loader for Mapbox Vector Tiles
Latest version: 4.2.0-alpha.2

# @loaders.gl/mvt

This module contains a geometry loader for Mapbox Vector Tiles (MVT).

[loaders.gl](https://loaders.gl/docs) is a collection of framework-independent visualization-focused loaders (parsers).
npm package: @globalfishingwatch/map-components
Description: Set of components used in global fishing watch world
Author: Satellite Studio
Latest version: 3.8.15

# ⚠️ LEGACY ⚠️ GFW map components

[![npm version](https://badge.fury.io/js/%40globalfishingwatch%2Fmap-components.svg)](https://badge.fury.io/js/%40globalfishingwatch%2Fmap-components)

All components has been moved to a [monorepo](https://github.com/GlobalFishingWatch/frontend/tree/master/packages/ui-components) and are now available at @globalfishingwatch/ui-components.

This repo only contains now legacy components used in data-portal and map-client

- Timebar (2.2 branch)
- MapModule

## Using the components

Check out the [online documentation](http://globalfishingwatch.io/map-components/)

## Components structure

```
component
│   component.js    // Component logic
│   component.css   // Component styles
│   component.mdx   // Generates component documentation
│   index.js // Optional file that generates a new folder below the components one
│            // and exports component code and any possible child component dependencies
│            // This makes possible components code splitting easily with
│            // import Component from '@globalfishingwatch/map-components/components/[component-name]
│
└───subcomponent
│       subcomponent.js
│       subcomponent.css
└───────────────────────
```

## Develop with components

In order to do easier edits on the components while developping parent apps, use this repo locally:

```bash
git clone git@github.com:GlobalFishingWatch/map-components.git
cd map-components
yarn install
yarn link
yarn start
```

```bash
cd sandbox
yarn install
yarn link "@globalfishingwatch/map-components"
yarn start
```

## Documentation

[Docz](https://www.docz.site/) is used to include live components documentation using mdx.

This playground could be used locally to test the components running:

```bash
yarn docz:dev
```

## Release

Using [zeit release](https://github.com/zeit/release) to make our life easier, so just run

```bash
npx release major|minor|patch
```

and it will update the package.json, generate the github release and push your changes and finally:

```bash
npm publish
```

(⚠️ don't forget to bump dependency version on parent project if needed!)
npm package: @globalfishingwatch/marine-regions
Description: A set of functions to retrieve localized list of marine regions
Author: GlobalFishingWatch
Latest version: 0.1.1

# Marine Regions

A set of functions to retrieve localized list of marine regions

## Install

yarn

```bash
yarn add @globalfishingwatch/marine-regions
```

npm

```bash
npm i @globalfishingwatch/marine-regions --save
```

## Usage

### Get EEZ regions

```js
import { getEEZ } from '@globalfishingwatch/marine-regions'
const regions = getEEZ({ locale: MarineRegionsLocale.en })
```

<details>
<summary>Output</summary>
<p>

```js
console.log(regions)
[
  { id: 5670, label: 'Albanian Exclusive Economic Zone' },
  { id: 8378, label: 'Algerian Exclusive Economic Zone' },
  { id: 8444, label: 'American Samoa Exclusive Economic Zone' },
  ....
]
```

</p>
</details>

### Get MPA regions

```js
import { getMPA } from '@globalfishingwatch/marine-regions'
const regions = getMPA()
```

<details>
<summary>Output</summary>
<p>

```js
console.log(regions)
[
  {"id": 12880, "label": "100_Daeseom"},
  {"id": 12910, "label": "101_Hogamseom"},
  {"id": 12892, "label": "102_Galmaeseom"},
  ....
]
```

</p>
</details>

### Get RFMO regions

```js
import { getRFMO } from '@globalfishingwatch/marine-regions'
const regions = getRFMO({ locale: MarineRegionsLocale.en })
```

<details>
<summary>Output</summary>
<p>

```js
console.log(regions)
[
  { id: 'CCSBT', label: 'CCSBT' },
  { id: 'IATTC', label: 'IATTC' },
  { id: 'ICCAT', label: 'ICCAT' },
  { id: 'IOTC', label: 'IOTC' },
  { id: 'WCPFC', label: 'WCPFC' },
  ....
]
```

</p>
</details>