2.3.1 • Published 3 years ago

@globalfishingwatch/timebar v2.3.1

Weekly downloads
109
License
MIT
Repository
github
Last release
3 years ago

Publish to npm

This monorepo hosts frontend packages and applications of the GlobalFishingWatch ecosystem.

Packages

All of them availables with the @globalfishingwatch/ prefix:

api-clientJS library to simplify GFW API login and resources fetch
dataviews-clientapi-client wrapper to fetch and edit dataviews and associated datasets/data
layer-composerOrchestrates various Layer Generators to generate a Mapbox GL Style document
pb-decodersPBF custom responses parsers
react-hooksSet of hooks to use libraries easily in react
timebarTimebar component, not many more to say
ui-componentsReusable atoms components kit

Applications

amatheaMarine reserve areas proyect
temporalgrid-demoCRA to show how new custom mapbox-gl format development goes
dataviews-editorSimple interface to edit dataviews
sandboxPlayground to use packages without releasing

Other utils

configShared generic build config as tsconfig, rollup or postcss
lintingDefine eslint prettier and stylelint configurations

See also

Mapbox GL / react-map-gl forks

We maintain our own forks of react-map-gl and Mapbox GL to handle gridded temporal data (see temporalgrid branches on both repos)

LayerComposer / Dataviews / Workspaces

See: From WebGL triangles to Dataviews - Organizing visualization of data at GFW

Dependencies

The repo is using yarn workspaces so npm is not suported yet, to install yarn follow this instructions

Install a new dependency

For all packages:

yarn add npm-package -W

Only for a specific package

yarn lerna add npm-package --scope=@scope/my-package

Installation

To install all packages dependencies just run:

yarn

Developmment

There is, for now, 3 package.json entry points to run the project:

  • Packages, to start the build of every package run:
yarn start:packages
  • Applications, to start any of them run;
yarn start:dataviews
yarn start:sandbox

To ensure git flow process, master branch will be protected to force opening PR to every change desired. For now, the only one strong recommendation is to tag every PR to prepare the changelog automatically.

Building

To test all packages builds process run, useful to test everything works well before publishing.

yarn build

Publishing

Using lerna-publish to versioning, tag and publish to npm every package individually Pending to have lerna-changelog working properly to auto generate the changelogs on PR labels

To release just run:

yarn release

And you will be prompt to select the new versions of the packages with changes since the last release.

2.3.1

3 years ago

2.3.0

3 years ago

2.2.0

3 years ago

2.1.0

3 years ago

2.0.7

3 years ago

2.0.8

3 years ago

2.0.6

3 years ago

2.0.5

3 years ago

2.0.4

3 years ago

2.0.3

3 years ago

2.0.2

3 years ago

2.0.1

3 years ago

2.0.0

3 years ago

1.8.0

3 years ago

1.7.0

3 years ago

1.5.3

3 years ago

1.6.1

3 years ago

1.5.2

3 years ago

1.6.0

3 years ago

1.5.1

3 years ago

1.5.0

3 years ago

1.4.1

3 years ago

1.4.0

3 years ago

1.3.3

3 years ago

1.3.2

3 years ago

1.3.1

3 years ago

1.3.0

3 years ago

1.2.1

3 years ago

1.2.0

3 years ago

1.1.6

3 years ago

1.1.5

3 years ago

1.1.4

3 years ago

1.1.3

3 years ago

1.1.2

3 years ago

1.1.1

4 years ago

1.1.0

4 years ago

1.0.15

4 years ago

1.0.14

4 years ago

1.0.13

4 years ago

1.0.12

4 years ago

1.0.11

4 years ago

1.0.10

4 years ago

1.0.8

4 years ago

1.0.6

4 years ago

1.0.4

4 years ago

1.0.3

4 years ago

1.0.2

4 years ago

1.0.1

4 years ago

1.0.0

4 years ago