api bump v-3.2.1

[niklabh]

• test auth server
• test node watcher
• test harvester
• test front end
• test chain db watcher

[Tbaut]

don't hesitate to seek help and open an issue on https://github.com/polkadot-js/api/ if there's anything you can't solve.
I'll take a quick look now.

[Tbaut]

What I did:

• follow the advice from the cli for auth-server linting by adding --resolveJsonModule
• bump many front-end deps avoiding some that required code change (such as semantic-ui that's not the goal of the PR)
• follow Can't import the named export x from non EcmaScript module (only default export is available) polkadot-js/extension#621 (comment) for the compiling issue.

Please make sure to triple-check the changes I made with the id params, and the councilMembers array. These were normal lint issues that came up because of the bump.

edit: a dependency bump needs to be made regularly, and many are still lacking. Not to mention the other projects such as auth-server that I didn't touch.

[niklabh]

Thankyou very much

[Tbaut]

Just a heads-up.
I bumped simple-import-sort, which resulted in lint error something like "cannot find simple-import-sort/sort rules".
You will 100% get the same in the other projects when bumping it as well.

[Tbaut]

A if could be needed here, I don't see why member would be undefined, but adding something like the following wouln't hurt:

Suggested change

	setCurrentCouncil([...currentCouncil, member?.address]);
	if (member)
	setCurrentCouncil([...currentCouncil, member.address]);
	}

[Tbaut]

The reason I did all these changes is because TS was complaining that "id can't be found in type {}".
The obvious problem here is the typing that is wrong (and this comes from @types/react-router-dom). I kind of when around it by using a hook that was there, and type correctly what I received with as string.

Another, maybe better way would be to keep using the useParams<Record<string, string>>(). Up to you what you prefer.

[niklabh]

There is memory leak/infinte loop in polkadot.js api or react-context.

This example can reproduce the issue

import React, {useContext, useEffect} from 'react';

import { ApiPromiseContext } from '@substrate/react-context';

function App() {
  const { api, isApiReady } = useContext(ApiPromiseContext);

  useEffect(() => {

		if (!isApiReady){
			return;
		}

    api.query.timestamp.now().then(console.log);

  }, [api, isApiReady]);

  return (
    <div>
      Memory leak
    </div>
  );
}

export default App;

[Tbaut]

@substrate/react-context has been upgraded afair, can you try with the earlier version? This is what changed, and could very well be the origin of the problem paritytech/substrate-js-utils@7172989#diff-8b186436e62efe7d5dd561abd16d87eddfb98281d8cbf8aef2ab6f6b0aabab86