|
@@ -50,6 +50,30 @@ Or if you are making only changes to the library:
|
50
|
50
|
npm install lib-jitsi-meet --force && make deploy-lib-jitsi-meet
|
51
|
51
|
```
|
52
|
52
|
|
|
53
|
+Alternative way is to use [npm link](https://docs.npmjs.com/cli/link).
|
|
54
|
+It allows to link `lib-jitsi-meet` dependency to local source in few steps:
|
|
55
|
+
|
|
56
|
+```bash
|
|
57
|
+cd lib-jitsi-meet
|
|
58
|
+
|
|
59
|
+# create global symlink for lib-jitsi-meet package
|
|
60
|
+npm link
|
|
61
|
+
|
|
62
|
+cd ../jitsi-meet
|
|
63
|
+
|
|
64
|
+# create symlink from the local node_modules folder to the global lib-jitsi-meet symlink
|
|
65
|
+npm link lib-jitsi-meet
|
|
66
|
+```
|
|
67
|
+
|
|
68
|
+So now after changes in local `lib-jitsi-meet` repository you can rebuild it with `npm run install` and your `jitsi-meet` repository will use that modified library.
|
|
69
|
+
|
|
70
|
+If you do not want to use local repository anymore you should run
|
|
71
|
+```bash
|
|
72
|
+cd jitsi-meet
|
|
73
|
+npm unlink lib-jitsi-meet
|
|
74
|
+npm install
|
|
75
|
+```
|
|
76
|
+
|
53
|
77
|
## Discuss
|
54
|
78
|
Please use the [Jitsi dev mailing list](http://lists.jitsi.org/pipermail/dev/) to discuss feature requests before opening an issue on Github.
|
55
|
79
|
|