live-plugin | IntelliJ plugin for writing IntelliJ plugins at runtime ⚡️ | Plugin library

by dkandalov Kotlin Version: v0.8.6beta License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | live-plugin Summary

live-plugin is a Kotlin library typically used in Plugin, Gradle applications. live-plugin has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

IntelliJ plugin for writing IntelliJ plugins at runtime ⚡️

Support

Quality

Security

License

Reuse

Support

live-plugin has a low active ecosystem.

It has 643 star(s) with 61 fork(s). There are 23 watchers for this library.

It had no major release in the last 12 months.

There are 28 open issues and 106 have been closed. On average issues are closed in 614 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of live-plugin is v0.8.6beta

Quality

live-plugin has no bugs reported.

Security

live-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

live-plugin is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

live-plugin releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of live-plugin

Get all kandi verified functions for this library.

live-plugin Key Features

No Key Features are available at this moment for live-plugin.

live-plugin Examples and Code Snippets

No Code Snippets are available at this moment for live-plugin.

Community Discussions

Trending Discussions on live-plugin

How to use electron to load the vue plugins installed dynamically into a plugins folder

QUESTION

How to use electron to load the vue plugins installed dynamically into a plugins folder

Asked 2019-Jul-05 at 19:28

I am using vue with electron to build a desktop application. I am using vue plugins to extend the functionality of the application. These vue plugins are hosted as npm modules in npm directory which can be installed from the applications plugin store using the live-plugin-manager which can be used to dynamically install plugins into plugins directory.

I am using webpack to compile the vue front-end. When I directly use these plugins, they work perfectly. I need to know if there is any way I can load these plugins dynamically from the folder each time application launches.

I have built the functionalities to install and uninstall the plugins. But I am unable to require these modules into the vue app. I tried using electron's remote.require call to fetch the module and using a loop called Vue.use() with the loaded plugin. But I keep on getting error.

...

ANSWER

Answered 2019-Jul-04 at 09:40

I was able to solve the issue by dynamic bundling of the plugins using browserify. I cannot share the entire code, but I will share the method I used.

First of all I included browserify into the dependency so that electron will include it in node_modules folder.
Then I set asar as false while packaging so that we can write into the app js file after bundling.
Each time the app starts it creates a js plugin loading script like:

Source https://stackoverflow.com/questions/56866935

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install live-plugin

Make sure "hello world" works fine:.
In the Plugins tool window select "hello-world" plugin and click "Run" button to execute the plugin (Run Plugin action with ctrl+shift+L or alt+C, alt+E shortcut). It should display a message.
Make a small modification in plugin.groovy/plugin.kts and rerun the plugin. On the second run, the previous version of the plugin will be unloaded before the code is evaluated again.
Modify plugin.groovy/plugin.kts file again so that it fails to compile/run. You should see an error message in the Run tool window.
Note that plugins are just folders with plugin.groovy or plugin.kts scripts as entry points. This means that you can, for example, copy the path to the plugin folder using the Copy Path action (ctrl/cmd+alt+C shortcut).
In the Plugins tool window click the "Plus" button (Add Plugin action) and add Groovy or Kotlin examples.
It might be useful to install Groovy or Kotlin plugin if your IDE supports them.
Run Plugins on IDE Start — run all plugins on IDE start.
Run Project Specific Plugins — run all plugins in .live-plugins project directory when the project is opened and unload them when the project is closed.
Add LivePlugin and IDE Jars to Project — useful for Groovy plugins to get auto-completion and code navigation in plugin code. (Adding jars unrelated to your project is a bit of a hack but there seems to be no major problems with it.) Note that Kotlin plugins should have auto-completion and code navigation without it.
Read (or at least skim) plugin development fundamentals.
Explore IntelliJ source code by cloning it, browsing it on GitHub or in Upsource. One useful strategy is to search for text you can see in IDE UI and then figure out how it's connected to the code which does the actual work.
PluginUtil class and liveplugin package might have some good starting points to explore IntelliJ API.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: