Post

Don McCurdy
@donmccurdy.com

What's the minimum feasible number transitive dependencies for maintaining and publishing a small JavaScript library with types? Assume: unit tests, bundle .ts sources to .js and .d.ts, and maybe shared lint-and-format settings.

Don McCurdy
@donmccurdy.com

Currently I'm using: biome, ava, c8, microbundle, and typescript. But even that short list gets a pretty regular stream of small updates and dependabot 'vulnerabilities' requiring updates across various repositories.

Don McCurdy
@donmccurdy.com

Vite+ (source-available, free for OSS) would presumably do all of that in one dependency? Though I haven't found Vite (have not tried Vite+) to be as good for bundling libraries as for building applications, so far.

0 reposts1 like

Kamran Ayub
@kamranicus.com

I mean, take a look at my simple guard utility for example lol github.com/kamranayub/t...

github.comGitHub - kamranayub/ts-has-guards: TypeScript utility types that augment built-in collection types like Map, Set, FormData, and URLSearchParams to offer type guarding capability to getters/settersTypeScript utility types that augment built-in collection types like Map, Set, FormData, and URLSearchParams to offer type guarding capability to getters/setters - kamranayub/ts-has-guards
Don McCurdy
@donmccurdy.com

Thanks! I realize my complaint above was vague, and no pressure to address this, but just in case it's helpful: the most recent issue that blocked me from using Vite's (current) library mode was related to sourcemaps: github.com/vitejs/vite/...

github.comFeature Request: Generating both dev and prod builds in library mode · Issue #1814 · vitejs/viteIs your feature request related to a problem? Please describe. I'm building a library and I want to generate output similar to what popular libraries like React and Vue do: esm + cjs/umd builds for...