Can @types/electron be removed as a devDependency?
See original GitHub issueI’m pulling ngx-electron into my project as a dependency, which has a dependency on @types/electron
, which appears to have a dependency on electron. This causes my Angular app’s node_modules to have a complete electron distribution in it, which it never uses. However, when I then use electron-builder, it dutifully pulls it in. According to this (https://www.npmjs.com/package/@types/electron), there is no reason to include @types/electron
anymore. Should it be removed entirely?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why does Electron need to be saved as a developer ...
The fact that you require a package is irrelevant to whether it should be considered a dependency or a devDependency (in the npm...
Read more >electron-react-typescript
A Boilerplate for an Easy Start with TypeScript, React, and Electron.. Latest version: 0.0.7, last published: 3 years ago.
Read more >@electron-forge/cli | Yarn - Package Manager
Electron Forge unifies the existing (and well maintained) build tools for Electron development into a simple, easy to use package so that anyone...
Read more >Creating Angular Desktop Apps with Electron
Before we can start working on our electron angular app, ... irrelevant for the running application, we add it as dev-dependency, as well....
Read more >What is Electron Microscopy?
The transmission electron microscope is used to view thin specimens (tissue sections, molecules, etc) through which electrons can pass generating a ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@walkingriver thanks for the input I’m closing this due to the currently working ‘workaround’ 😄 and the upcoming release mentioned in #11
thanks for the offer. I’ve just published
1.0.3
on npmjs perhaps can you try it in your scenario / build. I’ve tested and verified functionality with@angular/cli
based samples.@walkingriver
related to #10