Botpress: [FEATURE] Module-Builder as standalone npm package

Created on 8 Jul 2019 · 5Comments · Source: botpress/botpress

Is your feature request related to a problem? Please describe.

As a developer, I want my modules to be standalone, so that they can live in their own git repository and don't need any specific parent folder structure to build and work correctly.

As I want my modules to live in separate git repositories, I also want to exclude folders like .git/** from the packaging build phase, so that the .tar.gz file is as tiny as possible.

Describe the solution you'd like
Module Builder should be a standalone npm package, that simply can be specified in the package.json of a botpress-module and works out of the box.

wontfix

Source

crixx

❤2 👍2

Most helpful comment

Hi @marek-jarab

Just for clarification. So basically you want to delete all modules from botpress "main" project a have them as npm dependency situate on another git repo right?

What I want is the "module-builder" to be a standalone lib/cli, that can be used to build and package custom modules without the need to checkout the botpress main git repository.

At the time of the writing of this feature request, the process of developing a custom module was as follows:

download the botpress main git repo
copy the starter module and rename it
run yarn && yarn install in both, the created custom module as well as the main botpress repo
run "module builder", which is a proxy-script that uses the module builder living inside the main botpress repo

Is the process still the same with 12.1.5?

I'd like to have a standalone module-builder script, that can build and bundle custom botpress modules, which are not placed inside the botpress main repo...

Would be great to see this happen!
/crixx

crixx on 2 Oct 2019

👍3

All 5 comments

Hi. I would like to start working on this issue.Could you assign me pls?
Just for clarification. So basically you want to delete all modules from botpress "main" project a have them as npm dependency situate on another git repo right?

marek-jarab on 2 Oct 2019

Hi @marek-jarab

Just for clarification. So basically you want to delete all modules from botpress "main" project a have them as npm dependency situate on another git repo right?

What I want is the "module-builder" to be a standalone lib/cli, that can be used to build and package custom modules without the need to checkout the botpress main git repository.

At the time of the writing of this feature request, the process of developing a custom module was as follows:

download the botpress main git repo
copy the starter module and rename it
run yarn && yarn install in both, the created custom module as well as the main botpress repo
run "module builder", which is a proxy-script that uses the module builder living inside the main botpress repo

Is the process still the same with 12.1.5?

I'd like to have a standalone module-builder script, that can build and bundle custom botpress modules, which are not placed inside the botpress main repo...

Would be great to see this happen!
/crixx

crixx on 2 Oct 2019

👍3

+1 what Christian is suggesting, this would definitely be a great contribution and we would merge that as soon as possible!

slvnperron on 3 Oct 2019

Firstly, thanks for such a great project!

It would be really helpful also in my case - it would be great for my workflow to have a single git repo with a custom botpress module for my company, with build tools as devDependencies, without the need to create and maintain a fork of full botpress main repo.

Would be very happy to see a movement in such direction.

arcijsg on 16 Oct 2019

👍1

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.