Hey everyone !

I'd like to share a small plugin I just made : nodebb-plugin-save-plugins.
And the npm package : https://www.npmjs.com/package/nodebb-plugin-save-plugins
This plugin is meant to provide a way to store installed plugins and auto install them if they are missing.

This allows sharing plugins between multiple nodebb instances if needed.

I'm 100% open to feedback or suggestions !

Telokis

Just did https://github.com/NodeBB/NodeBB/issues/5564

I finally decided to migrate back to Github. I'll update the main post but here is the new link https://github.com/Telokis/nodebb-plugin-save-plugins

And the npm package : https://www.npmjs.com/package/nodebb-plugin-save-plugins

Feedback: Two days later, I'm totally in love with VSCode. It's really awesome and it made my life a lot easier! Thanks guys!

@PitaJ Yes, I know you did and thanks for that. However, I was hoping to be able to do it in another way in v1.4.5.

Hey everyone !

I don't like having to manually update the package.json file's patch version (the 'x' in '1.0.x').
Because of that, I decided to take advantage of git hooks and wrote some scripts to make my life easier.

You can find the scripts here but I'll make a dedicated repo if this seem useful to people.

Here is how it works:

• I assume everyone is setting up a tag for major/minor version changes ('x.x.0')
• I assume the scripts folder is at the root of the repository (to generate the hooks)

Then, after cloning a repo, I do this:

• cd scripts
• ./setup_hooks.sh

This will generate a post and a pre commit hook.
The pre-commit hook is used to automatically create a new tag if major or minor version has changed. Inside handle_tags.sh
The post-commit hook is used to automatically update the package.json after each commit. It increases the patch version by one (each commit is considered a patch) by counting the number of commits since the last tag (or the beginning if no tags made)
The post-commit hook (file setup_readme_version.sh) also updates the readme.md of my project to write
_Current repository version : v<major>.<minor>.<patch>_
If you don't want this behavior, you don't have anything to do. If you want it, you have to put
_Current repository version : v_ somewhere in your readme. The regexp will match and update it.

And, if you want to bump minor or major version, simply do it in your package.json and the hooks will properly read and process it. Even updating the readme. And a new tag will be created.

Let me know what you think about this stuff !

Just updated to 0.8.0:

• Added some unit tests to provide a more robust tool
• Updated the README.md with additional details
• Added a CLI version to ease usage
• Added default options system and new options
• A cache system to avoid reading the same file twice
• Possibility to output directly to a file
• Possibility to specify include paths to look into

Once again, I'm open to any feedback/suggestion/comment you could make!

Have a nice day!