Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
MIME-Version: 1.0
In-Reply-To: <CACK5iZdUu6WmY2oHy3H1e3Of7+9udAz_3Sa0qWZGgt9VzdDjKw@mail.gmail.com>
References: <CACK5iZdUu6WmY2oHy3H1e3Of7+9udAz_3Sa0qWZGgt9VzdDjKw@mail.gmail.com>
From: Josh Tynjala <joshtynjala@gmail.com>
Date: Mon, 22 Aug 2016 08:09:03 -0700
Message-ID: <CADZSWG4uFm12XDp4Ar8-QtCR1y0z8hu9OQ4z07UQOCox423_Dg@mail.gmail.com>
Subject: Re: FlexJS 0.7.0 - NPM installation issues
To: dev@flex.apache.org
Content-Type: multipart/alternative; boundary=001a1149923e265910053aaa7031
archived-at: Mon, 22 Aug 2016 15:09:51 -0000

--001a1149923e265910053aaa7031
Content-Type: text/plain; charset=UTF-8

One more thing that will be easy to miss:

The executable files like asjsc in js/bin have been tweaked a bit to
include different default compiler arguments. The NPM exectuables like
asjscnpm will need those same tweaks.

- Josh

On Fri, Aug 19, 2016 at 3:44 PM, OmPrakash Muppirala <bigosmallm@gmail.com>
wrote:

> I just tried the rc release with the current npm installation setup.
>
> First issue I see is this:
>
>
> Error: ENOENT: no such file or directory, scandir
> 'C:\Users\omuppirala\AppData\Roaming\npm\node_modules\
> flexjs\downloads\falcon\compiler\generated\dist\sdk\bin'
>
> In 0.6.0, we were copying files from the
> '...\downloads\falcon\compiler\generated\dist\sdk\bin' directory.  Did
> that
> get moved?
>
> Thanks,
> Om
>

--001a1149923e265910053aaa7031--