alvarolorentedev / electron-plugin Goto Github PK
View Code? Open in Web Editor NEWan electron plugin extension package
License: MIT License
an electron plugin extension package
License: MIT License
So, I tried to add a plugin from github, but it return me an error, plugin
maybe some more options an liberty from where the packages come, because, they don't need to be all from https://www.npmjs.com/
The build is a clean one from quick-start, using electron "^6.0.12" and Windows 10.
I tried several combos from (here )[https://docs.npmjs.com/cli/install] but some did get to an error, others blocked in some security walls for public access
Hi Alvaro,
in lifecycle.js you use module.paths and plugin.onLoad, but these attributes were added only during test/unit.
So your amazing plugin can only be used with your own tests. That's not neat a little.
This would be easier to have an idea of how to implement if we had a demo.
Can you add more detailed documentation? And then I wrote some ideas, do they fit in with your design? Look forward to your reply
Hi.
I'm not sure, this solution can be used to build a real plugin base system.
If a plugin doesn't have dependencies or have dependencies, which doesn't require any extra installation actions it will work. But, if the plugin has "complicated" dependency, which requires some extra installation actions, it will not.
You can try to create a plugin, which has as a dependency for example "node-pty". The thing is - node-pty does some extra installation actions. And npm can do it within some environment.
If you run electron application via terminal (something like "electron myapp.js" it could work, because in this case electron will use your environment.
But, if you will build an electron application and run it as a desktop application, the installation will be failed. Because your application will not use your environment anymore. For example, the variable PATH will not have your regular PATHs. As a result, during installation of node-pty will be an error, because npm/node cannot find python, which is needed to install node-pty.
So, to resolve this problem you should add PATH before call npm installation. But does it make sense? What if user of your application doesn't have on a board python? But to use and install plugin he has to install python?
Also not clear how you resolve an issue with necessary to rebuild some modules (https://electronjs.org/docs/tutorial/using-native-node-modules). Not sure, will be enough just install it plugin.
Also, this is not good idea to use programmatically npm. It doesn't looks like developers care about this way of usage. There are tons of documentation about CLI, but nothing about API.
So, definitely would be nice if you will provide more information about the usage of your solution.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.