Upgrade to Docusaurus V3

[lee00678]

This PR addresses the dependency vulnerabilities by upgrading to docusaurus v3.

It's a pretty big change, it includes some root folder package.json update as well. In order to use react and reactdom@18 (required for v3), we need to remove packages/website/package-loc.json from install:clean script. This way we can ensure the build uses react@18.

defaultProps in our mdx file will cause an error/warning message. This is caused by MDX scanning the docs and look for words like defaultProps, we don't actually use them in our doc, they are just javascript objects. So renamed the example props.

Added a new authors.yml file under releases, this way we no longer to copy over all the author information for each release article.

To test: In the root folder do a npm run install:clean, npm run build, then run npm run website.

[rokotyan]

Looks good! You may also want to update the Contributing section to mention Solid.

[rokotyan]

Surprised to see the React version change without any package.json updates

[lee00678]

Yea, good question. I think, based on my understanding, the react version gets hoisted to the parent level, so because of the later version in packages/website/package-lock.json, this become a later version.

[rokotyan]

I like this idea, but I find the name MyComponent sound a little bit too generic. Maybe DocsStackedBar instead?

[rokotyan]

defaultProps in our mdx file will cause an error/warning message. We need to start using defaultParams. I updated only the StackedBar.mdx as a test, once we agree on the approach, I will update the rest of the files.

@lee00678 Can you tell more about the defaultProps problem? What kind of error / warning?

[lee00678]

defaultProps in our mdx file will cause an error/warning message. We need to start using defaultParams. I updated only the StackedBar.mdx as a test, once we agree on the approach, I will update the rest of the files.

@lee00678 Can you tell more about the defaultProps problem? What kind of error / warning?

@rokotyan This is warning we are getting caused by defaultProps. It occurs on pages where defaultProps are used. Component pages, for example.

[rokotyan]

@lee00678 I believe this error comes from React and is related to React's defaultProps, not to our defaultProps` which are just simple JavaScript objects.

The only place where Unovis uses it is here:

unovis/packages/react/src/composites/time-series/index.tsx

Lines 107 to 112 in 793277d

	VisTimeSeries.defaultProps = {
	margin: { top: 10, bottom: 10, left: 10, right: 10 },
	autoMargin: true,
	padding: {},
	x: (d: VisTimeSeriesDatum) => d.timestamp,

But this component part is not being used anywhere. I thought of releasing something like this to give our users slightly more complex components, but now I don't think it's a good idea (I would rather share it as an example).

I've tried commenting it out but still seeing the warning, so maybe some our our or Docusaurus dependencies uses defaultProps

[lee00678]

Looks good! You may also want to update the Contributing section to mention Solid.

Resolved in a separate PR: #491

[lee00678]

@lee00678 I believe this error comes from React and is related to React's defaultProps, not to our defaultProps` which are just simple JavaScript objects.

The only place where Unovis uses it is here:

unovis/packages/react/src/composites/time-series/index.tsx

Lines 107 to 112 in 793277d

	VisTimeSeries.defaultProps = {
	margin: { top: 10, bottom: 10, left: 10, right: 10 },
	autoMargin: true,
	padding: {},
	x: (d: VisTimeSeriesDatum) => d.timestamp,

But this component part is not being used anywhere. I thought of releasing something like this to give our users slightly more complex components, but now I don't think it's a good idea (I would rather share it as an example).

I've tried commenting it out but still seeing the warning, so maybe some our our or Docusaurus dependencies uses defaultProps

I actually think this issue maybe simply caused by the fact we are calling them defaultProps, because for Line.mdx, we call it lineProps and the page is not erroring out. We could update the doc to avoid defaultProps and set to scatterProps etc. Since what we have is javascript object, maybe this is a better solution?

[rokotyan]

@lee00678 Maybe, let's try it

[lee00678]

@lee00678 Maybe, let's try it

That seems to fix all the defaultProps warnings.

[rokotyan]

@lee00678 Great! I didn't have any other comments so I think we can go ahead and merge this