ente/web/packages/utils/README.md

## @/utils

Utility functions, types and assortments.

> "Life is like a box of chocolates" - _Forrest Gump_

### Packaging

This (internal) package exports a vanilla TypeScript library. We rely on the
importing project to transpile and bundle it.
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 07:29:12 +00:00			`## @/utils`
Scaffold utils project 2024-02-14 13:15:51 +00:00
			`Utility functions, types and assortments.`
Integrate the actual one 2024-02-16 04:12:44 +00:00
			`> "Life is like a box of chocolates" - _Forrest Gump_`
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 07:29:12 +00:00
			`### Packaging`

			`This (internal) package exports a vanilla TypeScript library. We rely on the`
			`importing project to transpile and bundle it.`