beenull/ente
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ente/web/packages/build-config
History
Manav Rathi 1f4bac8fac
Update build-deps
2024-05-15 15:27:05 +05:30
..
.eslintrc.js Move into web/ 2024-03-01 12:21:07 +05:30
eslintrc-base.js Fix lint for web 2024-05-01 09:13:41 +05:30
eslintrc-next.js Restructure eslint config 2024-04-02 20:44:57 +05:30
eslintrc-react.js [web] Add ESLint to enforce HMR how vite likes it 2024-04-13 18:38:24 +05:30
eslintrc-vite.js Enable the jsx-runtime plugin for vite's ESLint 2024-04-04 14:46:41 +05:30
package.json Update build-deps 2024-05-15 15:27:05 +05:30
README.md prettier markdown 2024-04-03 13:39:44 +05:30
tsconfig-typecheck.json Convert payments app to use Vite - Part 1 2024-04-04 11:10:34 +05:30
tsconfig-vite.json Remove unused 404 handler 2024-04-04 13:58:30 +05:30
tsconfig-vite.node.json Convert payments app to use Vite - Part 1 2024-04-04 11:10:34 +05:30
tsconfig.json Fix the yarn lint 2024-04-05 21:22:44 +05:30

README.md

@/build-config

Build time configuration files. This can be thought of as a devDependency that exports various config files that our packages use at build time.

Packaging

This is not a TypeScript package, nor is it linted. It is not meant to be transpiled, it just exports static files that can be included verbatim.

Debugging

Too see what tsc is seeing (say when it is trying to type-check @/utils), use yarn workspace @/utils tsc --showConfig.

Similarly, to verify what ESLint is trying to do, use yarn workspace @/utils eslint --debug .

If the issue is in VSCode, open the output window of the corresponding plugin, it might be telling us what's going wrong there. In particular, when changing the settings here, you might need to "Developer: Reload Window" in VSCode to get it to pick up the changes.