Two issues on Windows - reflect-metadata missing and client app crash #185

Activity

1. BradRem commented on Jul 15, 2016

   

   BradRem

   on Jul 15, 2016

   More actions

   I was having both these issues, but after I added "reflect-metadata" to the "dependencies" under package.json, both issues were resolved.
2. tsmith-sdm commented on Jul 24, 2016

   

   tsmith-sdm

   on Jul 24, 2016

   More actions

   Adding the import 'reflect-metadata' to boot-client.ts resolved the issue for me but only when compiling and running from VS2015. If I pop out to a cmd prompt and run > dotnet run I still get the following error. This is also what breaks the counter page.

   Error: Cannot find module "reflect-metadata"
   /dist/main.js?v=NRyF4xz17BbBUvE2kfFqr5de-qY0BPjRSvLL1hWLrAk:1

   boot-client.ts:

   require('zone.js');
   import 'bootstrap';
   import 'reflect-metadata';
   import './styles/site.css';
   
3. justinhixson commented on Jul 27, 2016

   

   justinhixson

   on Jul 27, 2016

   More actions

   @tsmith-sdm I presume you meant adding the "reflect-metadata" to the "dependencies" under package.json, as @BradRem suggested? My boot-client.ts was correct out of the box, and I didn't need to add anything to it. I did have to do what @BradRem suggested, and as you stated, it only works when run from Visual Studio, and continues to fail when run from the command line.
4. SteveSandersonMS commented on Aug 16, 2016

   

   SteveSandersonMS

   on Aug 16, 2016

   Member

   More actions

   I'm pretty sure this is the same as #239 (and also mentioned in #82). reflect-metadata doesn't get installed properly on Windows if you're on NPM 2.x. You need NPM 3.x (as per docs).

   Note that just having installed NPM 3.x on your Windows machine doesn't mean that Visual Studio will use it, since VS has its own private copy of Node/NPM that it uses. Getting VS to use NPM 3.x is a bit more involved - see the "A FIX" heading on http://www.hanselman.com/blog/VisualStudio2015FixingDependenciesNpmNotInstalledFromFseventsWithNodeOnWindows.aspx

   If anyone's definitely on NPM 3.x (both when running from command line, and from VS, which has to be set up differently) and still gets this, please re-open!
5. SteveSandersonMS

   closed this as completedon Aug 16, 2016