[jitsi-dev] Developer mode in jitsi-meet


#1

Hi Group,

Please correct me if my understanding is wrong. In order to modify code and
develop for jitsi-meet we:
1 - clone lib-jitsi-meet
2 - npm install
Is this correct?

Also, this installs in production mode (minimized), I do see webpack -p
being passed when I run npm install. After this if I run "webpack -d" in
the command line it creates the files non-minimized files. Is this the
right way to generate non-minimized files?

Do we need to do anything elsewith the standard jitsi-meet sources? (to be
able to develop for jitsi-meet)

···

--
Thanks,
Sangram Rath


#2

1 - clone lib-jitsi-meet

I suppose you're modifying jitsi/lib-jitsi-meet then. If you're
modifying jitsi/jitsi-meet only, you do not need to clone
jitsi/lib-jitsi-meet.

2 - npm install

The command `npm install` installs the dependencies of the package in
which the command is executed. It's true that in
`jitsi/lib-jitsi-meet` we choose to build the minimized lib-jitsi-meet
library bundle. If you do not modify the dependencies in package.json
and want to speed up subsequent rebuilds, `npm install` is necessary
once and then you can run `./node_modules/.bin/webpack` to produce a
non-minimized bundle or `./node_modules/.bin/webpack -p` to produce a
minimized bundle.

Also, this installs in production mode (minimized), I do see webpack -p
being passed when I run npm install. After this if I run "webpack -d" in the
command line it creates the files non-minimized files. Is this the right way
to generate non-minimized files?

I use merely `./node_modules/.bin/wepack` myself but you can pass `-d`
if that's something you want to do.

Do we need to do anything elsewith the standard jitsi-meet sources? (to be
able to develop for jitsi-meet)

Well... I'm not really sure what you want to modify because you
mention both lib-jitsi-meet and jitsi-meet so:

1. If you modify jitsi/lib-jitsi-meet, then you need to make sure that
jitsi/jitsi-meet uses your rebuilt lib-jitsi-meet bundle. There are
multiple options here: `npm link` jitsi/lib-jitsi-meet, manually copy
lib-jitsi-meet{,.min}.js, modify and build directly in
jitsi-meet/node_modules/lib-jitsi-meet, etc.

2. If you modify jitsi/jitsi-meet, you're fine a initial `make` and
then just `./node_modules/.bin/webpack`. You may want to modify
index.html to not use app.bundle.min.js but app.bundle.js or you may
want to test locally with `./node_modules/.bin/webpack-dev-server`.

···

On Sat, Feb 11, 2017 at 12:03 AM, Sangram Rath <sangram.rath@gmail.com> wrote:


#3

Hi Lyubomir,

Thanks for the response, clears out a lot of stuff.
How can I generate a NON-MINIMIZED version of *jitsi-meet*? Or in
otherwords a development installation.
Same process you mentioned towards the end using webpack?

···

On Sat, Feb 11, 2017 at 11:19 PM, Lyubomir Marinov < lyubomir.marinov@jitsi.org> wrote:

On Sat, Feb 11, 2017 at 12:03 AM, Sangram Rath <sangram.rath@gmail.com> > wrote:
> 1 - clone lib-jitsi-meet

I suppose you're modifying jitsi/lib-jitsi-meet then. If you're
modifying jitsi/jitsi-meet only, you do not need to clone
jitsi/lib-jitsi-meet.

> 2 - npm install

The command `npm install` installs the dependencies of the package in
which the command is executed. It's true that in
`jitsi/lib-jitsi-meet` we choose to build the minimized lib-jitsi-meet
library bundle. If you do not modify the dependencies in package.json
and want to speed up subsequent rebuilds, `npm install` is necessary
once and then you can run `./node_modules/.bin/webpack` to produce a
non-minimized bundle or `./node_modules/.bin/webpack -p` to produce a
minimized bundle.

> Also, this installs in production mode (minimized), I do see webpack -p
> being passed when I run npm install. After this if I run "webpack -d" in
the
> command line it creates the files non-minimized files. Is this the right
way
> to generate non-minimized files?

I use merely `./node_modules/.bin/wepack` myself but you can pass `-d`
if that's something you want to do.

> Do we need to do anything elsewith the standard jitsi-meet sources? (to
be
> able to develop for jitsi-meet)

Well... I'm not really sure what you want to modify because you
mention both lib-jitsi-meet and jitsi-meet so:

1. If you modify jitsi/lib-jitsi-meet, then you need to make sure that
jitsi/jitsi-meet uses your rebuilt lib-jitsi-meet bundle. There are
multiple options here: `npm link` jitsi/lib-jitsi-meet, manually copy
lib-jitsi-meet{,.min}.js, modify and build directly in
jitsi-meet/node_modules/lib-jitsi-meet, etc.

2. If you modify jitsi/jitsi-meet, you're fine a initial `make` and
then just `./node_modules/.bin/webpack`. You may want to modify
index.html to not use app.bundle.min.js but app.bundle.js or you may
want to test locally with `./node_modules/.bin/webpack-dev-server`.

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Thanks,
Sangram K Rath