为什么 Electron 需要保存为开发者依赖?

The reason is also explained in the post you link to: when you publish your package, if the consumer project needs other packages to use yours, then these must be listed as dependencies.

如果您的包仅使用某些模块来构建、测试或将它们捆绑到 dist 文件中(即消费者项目将使用什么)，那么这些模块不应在 dependencies 中提及.我们仍然将它们列在 devDependencies 中以供开发使用.

If your package uses some modules only for build, test, or bundles them into a dist file (i.e. what will be used by the consumer project), then those modules should not be mentioned in dependencies. We still list them in devDependencies for development.

现在对于电子应用程序，您将应用程序作为消费者项目的节点模块使用的可能性很小，因此上述约定并不真正相关.

Now in the case of an electron app, there is little chance you will consume your app as a node module of a consumer project, therefore the above convention is not really relevant.

此外，我们还遇到了 electron 包被捆绑为构建输出的一部分的情况.您的用户无需从 npm 获取 electron 即可使用您构建的应用程序.因此它很好地匹配了 devDependency 的定义.

Furthermore, we fall in the case where the electron package is bundled as part of the built output. There is no need for your user to get electron from npm to use your built app. Therefore it matches well the definition of a devDependency.

话虽如此，IIRC 一些电子打包程序将您的 dependencies 捆绑到构建的应用程序中，因此您仍然需要严格地填写此列表.

That being said, IIRC some electron packagers bundle your dependencies into the built app, so you still need some rigour in filling this list.

这篇关于为什么 Electron 需要保存为开发者依赖?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！