Thanks for the detailed explanation, it's much clearer to me now!
On 07/05/2017 01:04 PM, Antranig Basman wrote:
> Cheers for the question, Gio.
>
> As of the merge of https://github.com/GPII/universal/pull/487 fixing
> GPII-2151, it *should* have been the case that all test cases will run
>
Yes, that is what I meant - sorry for the confusion.
On 05/07/2017 17:23, Tony Atkins wrote:
> Hi, Antranig.
>
> I assume you meant that /fluid.require("%universal")/ would solve the
> problem?
>
> Cheers,
>
>
> Tony
>
> On Wed, Jul 5, 2017 at 6:03 PM, Antranig Basman
>
Cheers for the question, Gio.
As of the merge of https://github.com/GPII/universal/pull/487 fixing
GPII-2151, it *should* have been the case that all test cases will run
properly regardless of the position of the checkout. They did at the
time of the merge - but with the universal truth that
Hello,
Regarding our requirement to have the universal live inside a node_modules
directory, could someone help me understand the machinery behind that? Since
some tests pass and others don't (when universal is not living inside
node_modules), does that mean this is a work in progress?
Hi
I think I've done something of interest to others. It's a bit of a hack,
but I've been able to (from within the Windows VM) use npm link and keep
the node_modules inside the VM.
All I wanted to do is put links inside node_modules (links that actually
look like links to Windows, and not have
