migration of @nivo/core to typescript and (partial) upgrade to React 18

[tkonopka]

Addresses #1219, #884 (partially)

Summary

• migrated @nivo/core to typescript
• moved @nivo/recompose from packages to deprecated.
• merged @nivo/tooltip into @nivo/core. They had mutual peer dependencies, and I couldn't get them to build separately.
• disabled stories and tests for non-typescript packages (affects line and waffle, also geo and parallel-coordinates). These packages are non-functioning in this branch.
• updated dependencies to React 18.1
• upgraded storybook to 6.5.9 to gain React 18 support
• adjusted all packages to use the new @nivo/core and pass build/lint/test
• further details are described in file packages/core/migration.md

Checks

• passes make init (building all packages from scratch)
• passes make packages-lint
• passes make packages-test (but non-typescript tests are disabled)
• runs make storybook and produces working charts (but non-typescript charts are disabled)

Open issues / questions

• compatibility with website
• storybook reports a warning about ReactDOM.render. It seems that despite having React 18 available, the pages run as if in React 17 mode. So compatibility with React 18 is unclear. (can someone help?)

@plouc, I set this as 'draft' to signal that it shouldn't be merged at this stage. But I hope some of it is useful. With your comments, we can extend this to address the issues, or move some material into smaller updates. Thanks!

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[willemmulder]

Great work!

[kacper-rogowski-wttech]

hi @plouc ,
Is there a chance, for you to take a look at this PR?

[willemmulder]

Bump pleeease! :-)

[srowe0091]

storybook reports a warning about ReactDOM.render. It seems that despite having React 18 available, the pages run as if in React 17 mode. So compatibility with React 18 is unclear. (can someone help?)

@tkonopka React 18 introduces a new way to render to the dom. here is what that looks like

// Before
import { render } from 'react-dom';
const container = document.getElementById('app');
render(<App tab="home" />, container);

// After
import { createRoot } from 'react-dom/client';
const container = document.getElementById('app');
const root = createRoot(container); // createRoot(container!) if you use TypeScript
root.render(<App tab="home" />);

PS. would love to get this into React 18

[tkonopka]

Hi @srowe0091. Yes, but that setup code is managed by storybook (nivo packages add components to an app that is already running). The appropriate initialization is supposed to be automatic, but here storybook seems to pick the pre-18 approach, which means the configuration or dependencies need adjustment. In a different project, I managed the switch by re-installing storybook from scratch, so that is an option.