| 1 |
On 07/04/2016 10:15 AM, Daniel Campbell wrote: |
| 2 |
> On 07/04/2016 12:57 AM, Nicolas Bock wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> I would like to package a code that depends on JavaScript packages. The |
| 6 |
>> suggested installation procedure from upstream involves running `npm |
| 7 |
>> install ...`. How do we (or do we?) deal with JavaScript packages? |
| 8 |
>> |
| 9 |
>> Best, |
| 10 |
>> |
| 11 |
>> Nick |
| 12 |
>> |
| 13 |
> The better question to ask is "what does this program need in order to |
| 14 |
> function?" If it installed through 'npm', that's going to point to Node. |
| 15 |
> Whatever format Node uses for its packages, you should read it and find |
| 16 |
> out if it requires anything else besides Node. If other Node packages |
| 17 |
> are needed, they may be in the tree already. |
| 18 |
> |
| 19 |
The program runs without JS. However, it can also run a server that |
| 20 |
provides a UI through a browser. That's the part that requires the JS. |
Archives