Judging by the package.json warning, it looks like you are installing it locally instead of globally. When you install locally, npm thinks that you're trying to add it as a dependency for a specific project, so it looks for a package.json file in the current directory.
Executables won't be added to the system path unless you install it globally. To do that, you need the -g flag: npm install -g Then, you can use asjsc without its full path. - Josh On Mon, Jan 4, 2016 at 11:30 AM, Harbs <[email protected]> wrote: > One comment: "Downloading Apache Falcon" is not correct. Falcon is a > separate Apache project. It should be Apache Flex Falcon Compiler. > > I tried installing and it does not look like it worked for me. > > Here’s the output at the end of the install: > > [email protected] node_modules/flexjs/node_modules/request -> > node_modules/request > /Users/harbs > └─┬ [email protected] > ├─┬ [email protected] > │ ├── [email protected] > │ └─┬ [email protected] > │ └── [email protected] > └─┬ [email protected] > ├─┬ [email protected] > │ └── [email protected] > ├─┬ [email protected] > │ ├── [email protected] > │ └─┬ [email protected] > │ └── [email protected] > └── [email protected] > > npm WARN ENOENT ENOENT: no such file or directory, open > '/Users/harbs/package.json' > npm WARN EPACKAGEJSON harbs No description > npm WARN EPACKAGEJSON harbs No repository field. > npm WARN EPACKAGEJSON harbs No README data > npm WARN EPACKAGEJSON harbs No license field. > > and I get asjsc not found when I try to run the command. > > FWIW, I do have flexjs inside node_modules in my User account. > > On Jan 4, 2016, at 8:47 PM, OmPrakash Muppirala <[email protected]> > wrote: > > > On Jan 4, 2016 10:02 AM, "Alex Harui" <[email protected]> wrote: > >> > >> > >> > >> On 1/4/16, 8:18 AM, "[email protected] on behalf of OmPrakash > Muppirala" > >> <[email protected] on behalf of [email protected]> wrote: > >> > >>> Oh right, forgot about that. > >>> > >>> npm uninstall flexjs -g > >>> > >>> Then clear cache and install. > >> > >> Clear what cache and how? I just tried it and it didn't work for me. > The > >> error looked the same so I think I may have still picked up an older > >> version. > > > > npm cache clear > > > > npm most likely picked up the tarball from the cache for you. > > > > Thanks, > > Om > > > >> > >> Thanks, > >> -Alex > >
