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

Why does Electron need to be saved as a developer dependency?(为什么 Electron 需要保存为开发者依赖?)
本文介绍了为什么 Electron 需要保存为开发者依赖?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

问题描述

根据官网,电子文件的正确保存方法是:

As per the official website, the correct way to save electron files is:

npm install electron --save-dev

运行应用程序实际上需要电子(字面意思是:require()),这与 最高投票答案.那么,如果这是一个例外,我们为什么要做出这个例外呢?

Electron is actually required for running the app (quite literally: require()) and this goes against the top voted answer here. So why do we make this exception, if this is even one?

推荐答案

require 一个包的事实与它是否应该被视为依赖项或 devDependency 无关(在 npm 意义上).例如.许多项目使用 webpack API(即 const webpack = require('webpack')),但将其列为 devDependency.

The fact that you require a package is irrelevant to whether it should be considered a dependency or a devDependency (in the npm sense). E.g. many projects use webpack API (i.e. const webpack = require('webpack')) but list it as a devDependency.

原因在你链接到的帖子中也有解释:当你发布你的包时,如果消费者项目需要其他包来使用你的包,那么这些必须列为 dependencies.

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 需要保存为开发者依赖?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

Google apps script get range of bytes from binary file(谷歌应用程序脚本从二进制文件中获取字节范围)
Sending Multiple attachments with Google Script from Google Drive(使用 Google 脚本从 Google Drive 发送多个附件)
Distributing Google Apps Scripts for Sheets in your company network(在您的公司网络中分发适用于表格的 Google Apps 脚本)
Upload file to my google drive from anyone using javascript(使用 javascript 将文件从任何人上传到我的谷歌驱动器)
quot;Shared Drivequot; support in Google Apps Script(“共享驱动器Google Apps 脚本中的支持)
Angular 2+ HTTP POST and GDrive API. Resumable file upload with name(Angular 2+ HTTP POST 和 GDrive API.带名称的可恢复文件上传)