On 03/11/2016 03:33 AM, Tom Hughes wrote:
> On 10/03/16 16:20, Stephen Gallagher wrote:
>> On 03/10/2016 06:32 AM, Stephen Gallagher wrote:
>>
On Mar 10, 2016, at 4:43 AM, Tom Hughes wrote:
- The npm doesn't work at all because all the bundled modules are in
On 03/11/2016 03:33 AM, Tom Hughes wrote:
> On 10/03/16 16:20, Stephen Gallagher wrote:
>> On 03/10/2016 06:32 AM, Stephen Gallagher wrote:
>>
On Mar 10, 2016, at 4:43 AM, Tom Hughes wrote:
- The npm doesn't work at all because all the bundled modules are in
On 10/03/16 16:20, Stephen Gallagher wrote:
On 03/10/2016 06:32 AM, Stephen Gallagher wrote:
On Mar 10, 2016, at 4:43 AM, Tom Hughes wrote:
- The npm doesn't work at all because all the bundled modules are in
the node_modules.bundled directory and node_modules is empty -
On 03/10/2016 12:25 PM, Tom Hughes wrote:
> On 10/03/16 16:20, Stephen Gallagher wrote:
>
>> I've just pushed a new update to the repository that also includes Node.js
>> 5.8.0
>> (released yesterday). Of course, since the minor version jumped, binary
>> packages
>> may need a rebuild.
>>
>> If
On 10/03/16 16:20, Stephen Gallagher wrote:
I've just pushed a new update to the repository that also includes Node.js 5.8.0
(released yesterday). Of course, since the minor version jumped, binary packages
may need a rebuild.
If we're going to look into supporting the rapidly-updating 5.x
On 03/10/2016 06:32 AM, Stephen Gallagher wrote:
>
>
>> On Mar 10, 2016, at 4:43 AM, Tom Hughes wrote:
>>
>>> On 08/03/16 21:32, Stephen Gallagher wrote:
>>>
>>> I put together a COPR that all of the Node.js SIG member have access to at
>>>