ente/docs/Dependencies.md
Manav Rathi a9a810ab99 Add typescript configuration in eslint
VSCode still gives an error

We had to set the type to module to get the `import` to work. Setting .mjs
didn't work (eslint didn't recognize the file). Setting the type to module
should be (based on my current understanding) not affect us negatively since we
are exporting a TypeScript library not a bundled one, and all the other source
files apart from this are intended to be `*.ts`.

Refs:
- https://jeremyrichardson.dev/blog/saga_of_learning_exports_property_in_packagejson
- https://github.com/eslint/eslint/discussions/17021
2024-02-16 20:48:26 +05:30

541 B

Dependencies

Global

These are some global dev dependencies in the root package.json. These set the baseline for how our code be in all the workspaces in the monorepo.

  • "prettier" - Formatter
  • "eslint" - Linter
  • "typescript" - Type checker

They also need some support packages:

  • "@typescript-eslint/parser" - Tells ESLint how to read TypeScript syntax

    TODO(MR): This is no longer needed with the new flat format.

  • "typescript-eslint" - TypeScript support for ESLint

    TODO(MR): Move this to the top level package.json