I also don't like repetitive work, but I think it can be beneficial to understand how the tools you use work, and bun/Deno seem to abstract much of it away.

Random example: I've worked with many frontend developers who seemed to believe listing dependencies in package.json in devDependencies instead of 'dependencies' controls what ends up in the production bundle.

I'm under the impression few understand that this is only a cosmetic distinction unless you use the package manager's --omit=dev or --production flags during install.

What is included in the production bundle is of course determined by the bundler's dependency-graph reachability from the entry point.

For people who never configured these tools themselves, it's probably difficult to understand how the modern web stack works.

However, nowadays you can probably have AI explain it to you well enough while it fixes the issues.

▲

KronisLV 6 hours ago | parent | next [-]

Silly drive by take:

> I've worked with many frontend developers who seemed to believe listing dependencies in package.json in devDependencies instead of 'dependencies' controls what ends up in the production bundle.

If so many believe that it’s how it should work, maybe it just should work that way. Principle of least surprise and all that.

▲

8n4vidtmkvmk 5 hours ago | parent [-]

You can and probably should set up your production builds that way but it's not automatic.

It also gets messy if you're building 2 or 3 services simultaneously out of the same node_modules dir. E.g frontend, backend, shared, scripts...

▲

user43928 5 hours ago | parent [-]

How would you set that up?

Like say you installed only the production dependencies, then you'd be missing the build tools, bundler, etc.

One idea would be to use hooks of your bundler to enforce that each module resolved during the production build is declared in the regular dependencies.

It would be far from a standard solution though.

▲

andrewaylett 12 minutes ago | parent | next [-]

https://github.com/import-js/eslint-plugin-import/blob/HEAD/...

It's not built in to ESLint, but it's fairly widely used in my experience and helps ensure that you've got a sensible split between production and non-production.

▲

mikeryan 2 hours ago | parent | prev [-]

NX Monorepos work that way. Broadly speaking (and with many exceptions) all packages end up in the root. It “builds” release distributions with the correct package.json files and transpiled js.

It helps keep all your related packages on the same dependencies. It’s hell for react native sometimes though.

	▲	user43928 an hour ago \| parent [-]
		I don't see what you mean. With nx you define the dependencies between your tasks, so that the packages build in the right order and with caching. I do not think it changes anything about how packages are installed by the package manager or bundled by the bundler. You can declare build tools in either the root package.json or packages/a/package.json, and I don't think anything prevents you from bundling something declared in devDependencies. On second thought, I see now that you probably mean it helps keep shared dependencies at the same version when you declare them in the root package.json. That's a feature of npm/pnpm/yarn workspaces though, not nx itself. And it only works with bundled dependencies, since they would be undeclared in the package itself and thus couldn't be installed externally. If you need that, I think pnpm catalogs would be the right tool.

▲

zamadatix 6 hours ago | parent | prev [-]

One should understand how their tools work but there's no such thing as doing that without understanding things across the abstractions involved and at least a good portion of what happens under them, Deno or not.

It works the same way you use a bundler instead of assembling your own and so on and so forth down the tree. The farther down the tree, the less focus you should give your understanding to, but that's not an excuse for giving no understanding below the first layer.