Web development MOC

• dependencies Needed at runtime/buildtime
• devDependencies Needed just at buildtime - not installed by consumers of the library
• peerDependencies Use a package without having consumers to install it - Expect consumers to be using a range of versions of the dependency that your library will be able to handle
• optionalDependencies Can or not use a depepdency and keep working without it

Better organisation
Different bindings i.e. svelte entrypoint vs nextjs entrypoint

"exports": {
// Single entry point,
//import {expored} from "package"
	".": : "./dist/index.js" 

//Multi-entry point 
//import {expored} from "package/components"
	"./components": "./dist/components" 
},

They export raw .ts files, leaving the responsibility to transpile it to JavaScript to the consuming application (On-Demand)
Pros

1. Low-configuration way to create internal packages

Cons

1. No build caching, since there’s no build step
2. Can’t use ts compiler options for import paths
3. Errors in these packages will propagate to importing apps
4. Worst editor performance

"exports": {
	".": : "./src/index.ts"
}

They export .js files that have already been pre-built, making it easier to cache and distribute.
Pros
Cons

"exports": {
	".": : "./dist/index.js"
},
"scripts": {
	"dev": "tsc --watch --preserveWatchOptions",
	"build": "tsc",
}
// tsconfig.json

"compilerOptions": {
	"outDir": "dist"
}
// Add