Experimental Plugins

A repo to test and experiment with plugins for Lume.

If you are using any of these plugins in your projects, keep in mind that it can be removed at any time for several reasons:

• It's moved to Lume main repo.
• A new plugin has been created to replace it.
• It's too unstable or not useful

For these reasons, it's high recommended to import a specific commit, using the commit hash in the url (https://raw.githubusercontent.com/lumeland/experimental-plugins/[hash]/[plugin]/mod.ts)

For example:

// Not recommended
import plugin from "https://raw.githubusercontent.com/lumeland/experimental-plugins/main/plugin/mod.ts";

// Recommended
import plugin from "https://raw.githubusercontent.com/lumeland/experimental-plugins/69b551c39a3000b1feaf0b2d5675b4cde92141c3/plugin/mod.ts";

Contributing

If you use Deno plugins for vscode and you don't enable Deno on user scope. Your vscode will not able to use the correct deno.json file. While it is ok for building/testing, this can cause a productivity problem (ex. type checking suggestion). To avoid this, you need to:

1. create .vscode/setting.json in the plugin dir, that you plan to work on, by cloning .vsode from top repo to the plugin dir (copy&paste).
2. Then open the plugin dir in new workspace.

Aside from /.vscode in top level repo, the rest .vscode are ignored by Git.