Re: [pgadmin-hackers] [patch] Refactor: clipboard, translations, jasmine - Mailing list pgadmin-hackers

accidentally removed the group from this thread. adding them back.

On Mon, Mar 13, 2017 at 7:08 AM, Dave Page <dpage@pgadmin.org> wrote:

On Fri, Mar 10, 2017 at 4:53 PM, Atira Odhner <aodhner@pivotal.io> wrote:
> We moved package.json, karma.conf, and node_modules under web. We'll take a

This doesn't work for me:

==========
(pgadmin4)piranha:web dpage$ sudo port install nodejs7 yarn
--->  Computing dependencies for nodejs7
--->  Fetching archive for nodejs7
--->  Attempting to fetch nodejs7-7.7.2_0.darwin_16.x86_64.tbz2 from
https://packages.macports.org/nodejs7
--->  Attempting to fetch nodejs7-7.7.2_0.darwin_16.x86_64.tbz2.rmd160
from https://packages.macports.org/nodejs7
--->  Installing nodejs7 @7.7.2_0
--->  Activating nodejs7 @7.7.2_0
--->  Cleaning nodejs7
--->  Computing dependencies for yarn
--->  Fetching archive for yarn
--->  Attempting to fetch yarn-0.21.3_0.darwin_16.noarch.tbz2 from
https://packages.macports.org/yarn
--->  Attempting to fetch yarn-0.21.3_0.darwin_16.noarch.tbz2.rmd160
from https://packages.macports.org/yarn
--->  Installing yarn @0.21.3_0
--->  Activating yarn @0.21.3_0
--->  Cleaning yarn
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.
--->  Some of the ports you installed have notes:
  yarn has the following notes:
    yarn stores data in:

        ~/.yarn
        ~/.yarnrc
        ~/.cache/yarn
        ~/.config/yarn

    Should you choose to install packages globally with yarn (yarn
global add), these files will not be removed if you deactivate or
uninstall yarn. By default, these packages
    will be installed in ~/.config/yarn/global, and soft-linked to
/opt/local/bin. To uninstall them all:

    $ ls -1 $HOME/.config/yarn/global/node_modules/  | xargs sudo yarn
global remove

    You may then remove the directories listed above and uninstall yarn.

    yarn is meant to replace NPM, and may cause conflicts if you use both.

    You may override the default global installation directory by
setting the PREFIX environment variable, e.g.

    mkdir -p $HOME/.config/yarn/bin # Or wherever you want
    export PREFIX=$HOME/.config/yarn/bin
    export PATH=$PREFIX:$PATH
(pgadmin4)piranha:web dpage$ yarn
yarn install v0.21.3
info No lockfile found.
[1/4] 🔍  Resolving packages...
success Nothing to install.
success Saved lockfile.
✨  Done in 0.17s.
(pgadmin4)piranha:web dpage$ sudo npm install -g karma-cli
/opt/local/bin/karma -> /opt/local/lib/node_modules/karma-cli/bin/karma
/opt/local/lib
└── karma-cli@1.0.1

(pgadmin4)piranha:web dpage$ karma start --single-run
Cannot find local Karma!
  Please install Karma by `npm install karma --save-dev`.
  If you wanna use a global instance, please set NODE_PATH env variable.
==========

I tried setting NODE_PATH to various seemingly obvious values (e.g.
/opt/local, /opt/local/lib/node_modules) but it still wouldn't work.
Google is not helping.

This also highlighted the fact that the README changes are specific to
homebrew on macOS only. At the very least they need to point out that
and that users may need to adapt to other commands on Linux/Windows or
if using MacPorts for example.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company