Update rush config files. Adds lint rules. Add pre-commit hook. Removes pre-push hook

[alber70g]

• chore: update rush.json configuration
• chore: adds boilerplate to .pnpmfile.js
• chore: adds engines to prevent usage of npm or yarn
• chore: ignore lockfiles
• chore: remove .vscode/settings.json in favor of .editorconfig and .prettierrc in combination with pre-commit lint-/autofix-rules
• chore(lint): adds strict and relevant lint rules

What:
Improve the monorepo by setting sane defaults in rush.json
Adds preinstall script to prevent non-pnpm being used
Removes .vscode editor settings, in favor of .editorconfig and .prettierrc with pre-commit lint rules

[Randynamic]

can we maybe move the types to a types folder in this repo as well as we are doing a significant rewrite and rearranging of the folder structure

[alber70g]

Yes that's a good one. Maybe we need to work on a base set of types to be used. I'm not a big fan of a separate types library. They can become overused, especially when they're broader than what's used in a function.

E.g.

// defined in @kadena/types
export type SomeGenericType = {
  name: string;
  color: 'blue' | 'red' | 'green';
};


// defined in @kadena/some-lib
import type { SomeGenericType } from '@kadena/types';

function getName({ name }: SomeGenericType) {
  return name;
}

In this example the SomeGenericType is way to broad for the usage. I'd rather have it exported and defined specifically, than made generic:

// defined in @kadena/some-lib
export type MySpecificType = {
  name: string;
};

function getName({ name }: MySpecificType) {
  return name;
}

Also, api-extractor can manage the type defenition .d.ts. generation based on public, alpha, beta, non-private JS/TSdoc

[Randynamic]

I like the api-extractor for for sure indeed.
Let's have a discussion about the types folder or not in our next dev experience meeting so we are all onboard

[Randynamic]

Sweet!