EC

Effect Community•3y ago•

348 replies

addamsson

Questions about Codebase of Effect: Use of vitest instead of vite and absence of types in package...

I have been perusing the codebase of effect (not the code yet, but how it is built) and I have a few questions about it:
- I can see that you're using

vitest

vitest

, is there a reason for not using

vite

vite

for building? (I can see that

tsc

tsc

is used)
- minor detail, but I can't see

types

types

in any of the

package.json

package.json

files. in theory npm (the package repository) will only show

effect

effect

as a

TS

TS

project if this field is included, but I can still see

TS

TS

on npm! do you have any idea why?
- the

.vscode

.vscode

directory is committed into the repository. this prevents some people with reading problems to contribute to the project because they can't have their own custom config. prettier is a good example, I always override the tab width to

4

4

because I can't read the code with

2

2

properly. do you have any other way for contributors to override the config? (without having to resort to manually fiddling with the values before / after every commit)
- I looked and I couldn't find docs about some tool choices in the project that are not mentioned in the README. I know

madge

madge

for example, but I have no idea what

.nix

.nix

files do, or what

flake

flake

is