First, let me say it sucks that the dev tools built into the browser are being deprecated. It was so approachable, quick and not intimidating. Plus the deprecation notice sends you to https://github.com/itslenny/PowerBI-visuals/blob/master/CliToolsSoon.md which is kinda weird imo, and unclear if its current/correct. Says there will be hot new freshness "in a few weeks", but that was posted a month ago.
Anyway, once you get to https://github.com/Microsoft/PowerBI-visuals... you are scared 🙂 And rightfully so. multiple installers or package managers and ... well, it doesn't work for me anyway.
Any suggestions here?
C:\Users\Scott\Dropbox (Personal)\src\pbi\PowerBI-visuals>npm install
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli '2' ]
2 info using npm@3.0.0
3 info using node@v4.4.7
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly rollbackFailedOptional Starting
8 silly rollbackFailedOptional Finishing
9 silly runTopLevelLifecycles Starting
10 silly runTopLevelLifecycles Finishing
11 silly install printInstalled
12 verbose stack Error: ENOENT: no such file or directory, open 'C:\Users\Scott\Dropbox (Personal)\src\pbi\PowerBI-visuals\node_modules\body-parser\package.json'
12 verbose stack at Error (native)
13 verbose cwd C:\Users\Scott\Dropbox (Personal)\src\pbi\PowerBI-visuals
14 error Windows_NT 10.0.10586
15 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "2"
16 error node v4.4.7
17 error npm v3.0.0
18 error path C:\Users\Scott\Dropbox (Personal)\src\pbi\PowerBI-visuals\node_modules\body-parser\package.json
19 error code ENOENT
20 error errno -4058
21 error syscall open
22 error enoent ENOENT: no such file or directory, open 'C:\Users\Scott\Dropbox (Personal)\src\pbi\PowerBI-visuals\node_modules\body-parser\package.json'
22 error enoent This is most likely not a problem with npm itself
22 error enoent and is related to npm not being able to find a file.
23 verbose exit [ -4058, true ]
