This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Microsoft.DotNet.Props was not found #456
Description
Windows 10 x64
node v6.7.0
npm v4.0.2
.NET Core 1.0.1 tools Preview 2
.NET Core 1.1 SDK
tsc v2.0.10 (same results with v1.8)
VS Code
VS2015
VS2017
I get the following error when I run the React generator (yarn v0.17.8):
C:\MyFiles\ViewModel\repros\wReact>yo
? 'Allo ManuelDeLeon! What would you like to do? Aspnetcore Spa
Make sure you are in the directory you want to scaffold into.
This generator can also be run with: yo aspnetcore-spa
_-----_ ╭──────────────────────────╮
| | │ Welcome to the ASP.NET │
|--(o)--| │ Core Single-Page App │
`---------´ │ generator! │
( _´U`_ ) ╰──────────────────────────╯
/___A___\ /
| ~ |
__'.___.'__
´ ` |° ´ Y `
? Framework React
? Your project name wReact
Will restore NPM dependencies using 'yarn' installed at C:\Users\manuel.de.leon\AppData\Roaming\npm\yarn.CMD
I'm all done. Running npm install for you to install the required dependencies. If this fails, try running the command yourself.
create package.json
create .babelrc
create appsettings.json
create ClientApp\boot.tsx
create ClientApp\components\Counter.tsx
create ClientApp\components\FetchData.tsx
create ClientApp\components\Home.tsx
create ClientApp\components\Layout.tsx
create ClientApp\components\NavMenu.tsx
create ClientApp\css\site.css
create ClientApp\routes.tsx
create Controllers\HomeController.cs
create Controllers\SampleDataController.cs
create Dockerfile
create package.json.tmp
create Program.cs
create project.json
create README.md
create Startup.cs
create .gitignore
create node_modules\_placeholder.txt
create WReact.xproj
create tsconfig.json
create Views\_ViewImports.cshtml
create Views\_ViewStart.cshtml
create Views\Home\Index.cshtml
create Views\Shared\_Layout.cshtml
create Views\Shared\Error.cshtml
create web.config
create webpack.config.js
create webpack.config.vendor.js
create wwwroot\dist\_placeholder.txt
create wwwroot\favicon.ico
yarn install v0.17.8
info No lockfile found.
warning WReact@0.0.0: No license field
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@types%2freact-router: self signed certificate in certificate chain".
info If you think this is a bug, please open a bug report with the information provided in "C:\\MyFiles\\ViewModel\\repros\\wReact\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
C:\MyFiles\ViewModel\repros\wReact\WReact.xproj(8,3): error MSB4019: The imported project "C:\Program Files\dotnet\sdk\1.0.0-preview3-004056\Extensions\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
The system cannot find the path specified.
The system cannot find the path specified.
_-----_ ╭───────────────────────╮
| | │ Bye from us! │
|--(o)--| │ Chat soon. │
`---------´ │ Yeoman team │
( _´U`_ ) │ http://yeoman.io │
/___A___\ /╰───────────────────────╯
| ~ |
__'.___.'__
´ ` |° ´ Y `
By the way, with yarn v0.16.1 I get the following set of errors:
C:\MyFiles\ViewModel\repros\wReact>yo
? 'Allo ManuelDeLeon! What would you like to do? Aspnetcore Spa
Make sure you are in the directory you want to scaffold into.
This generator can also be run with: yo aspnetcore-spa
_-----_ ╭──────────────────────────╮
| | │ Welcome to the ASP.NET │
|--(o)--| │ Core Single-Page App │
`---------´ │ generator! │
( _´U`_ ) ╰──────────────────────────╯
/___A___\ /
| ~ |
__'.___.'__
´ ` |° ´ Y `
? Framework React
? Your project name wReact
Will restore NPM dependencies using 'yarn' installed at C:\Users\manuel.de.leon\AppData\Roaming\npm\yarn.CMD
I'm all done. Running npm install for you to install the required dependencies. If this fails, try running the command yourself.
create package.json
create .babelrc
create appsettings.json
create ClientApp\boot.tsx
create ClientApp\components\Counter.tsx
create ClientApp\components\FetchData.tsx
create ClientApp\components\Home.tsx
create ClientApp\components\Layout.tsx
create ClientApp\components\NavMenu.tsx
create ClientApp\css\site.css
create ClientApp\routes.tsx
create Controllers\HomeController.cs
create Controllers\SampleDataController.cs
create Dockerfile
create package.json.tmp
create Program.cs
create project.json
create README.md
create Startup.cs
create .gitignore
create node_modules\_placeholder.txt
create WReact.xproj
create tsconfig.json
create Views\_ViewImports.cshtml
create Views\_ViewStart.cshtml
create Views\Home\Index.cshtml
create Views\Shared\_Layout.cshtml
create Views\Shared\Error.cshtml
create web.config
create webpack.config.js
create webpack.config.vendor.js
create wwwroot\dist\_placeholder.txt
create wwwroot\favicon.ico
yarn install v0.16.1
info No lockfile found.
warning WReact@0.0.0: No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
warning fsevents@1.0.15: The platform "win32" is incompatible with this module.
info "fsevents@1.0.15" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[1/1] ⠁ fsevents: node-pre-gyp ERR!
[-/1] ⠁ waiting...
[-/1] ⠁ waiting...
[-/1] ⠁ waiting...
error Error running install script for optional dependency: "C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents: Command failed.\nExit code: 1\nCommand: C:\\windows\\system32\\cmd.exe\nArguments: /d /s /c node-pre-gyp install --fallback-to-build\nDirectory: C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\nOutput:\nnode-pre-gyp info it worked if it ends with ok\nnode-pre-gyp info using node-pre-gyp@0.6.29\nnode-pre-gyp info using node@6.7.0 | win32 | x64\nnode-pre-gyp info check checked for \"C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node\" (not found)\nnode-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v48-win32-x64.tar.gz\nnode-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v48-win32-x64.tar.gz\nnode-pre-gyp ERR! Tried to download: https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v48-win32-x64.tar.gz \nnode-pre-gyp ERR! Pre-built binaries not found for fsevents@1.0.15 and node@6.7.0 (node-v48 ABI) (falling back to source compile with node-gyp) \nnode-pre-gyp http Pre-built binary not available for your system, looked for https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v48-win32-x64.tar.gz \n\r\nC:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents>if not defined npm_config_node_gyp (node \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\bin\\node-gyp-bin\\\\..\\..\\node_modules\\node-gyp\\bin\\node-gyp.js\" clean ) else (node clean ) \r\ngyp info it worked if it ends with ok\ngyp info using node-gyp@3.4.0\ngyp info using node@6.7.0 | win32 | x64\ngyp info ok \n\r\nC:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents>if not defined npm_config_node_gyp (node \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\bin\\node-gyp-bin\\\\..\\..\\node_modules\\node-gyp\\bin\\node-gyp.js\" configure --fallback-to-build --module=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node --module_name=fse --module_path=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64 ) else (node configure --fallback-to-build --module=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node --module_name=fse --module_path=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64 ) \r\ngyp info it worked if it ends with ok\ngyp info using node-gyp@3.4.0\ngyp info using node@6.7.0 | win32 | x64\ngyp info spawn C:\\Python27\\python.EXE\ngyp info spawn args [ 'C:\\\\Users\\\\manuel.de.leon\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\yarn\\\\node_modules\\\\node-gyp\\\\gyp\\\\gyp_main.py',\ngyp info spawn args 'binding.gyp',\ngyp info spawn args '-f',\ngyp info spawn args 'msvs',\ngyp info spawn args '-G',\ngyp info spawn args 'msvs_version=auto',\ngyp info spawn args '-I',\ngyp info spawn args 'C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\build\\\\config.gypi',\ngyp info spawn args '-I',\ngyp info spawn args 'C:\\\\Users\\\\manuel.de.leon\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\yarn\\\\node_modules\\\\node-gyp\\\\addon.gypi',\ngyp info spawn args '-I',\ngyp info spawn args 'C:\\\\Users\\\\manuel.de.leon\\\\.node-gyp\\\\6.7.0\\\\include\\\\node\\\\common.gypi',\ngyp info spawn args '-Dlibrary=shared_library',\ngyp info spawn args '-Dvisibility=default',\ngyp info spawn args '-Dnode_root_dir=C:\\\\Users\\\\manuel.de.leon\\\\.node-gyp\\\\6.7.0',\ngyp info spawn args '-Dnode_gyp_dir=C:\\\\Users\\\\manuel.de.leon\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\yarn\\\\node_modules\\\\node-gyp',\ngyp info spawn args '-Dnode_lib_file=node.lib',\ngyp info spawn args '-Dmodule_root_dir=C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents',\ngyp info spawn args '--depth=.',\ngyp info spawn args '--no-parallel',\ngyp info spawn args '--generator-output',\ngyp info spawn args 'C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\build',\ngyp info spawn args '-Goutput_dir=.' ]\nTraceback (most recent call last):\r\n File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\gyp_main.py\", line 16, in <module>\r\n sys.exit(gyp.script_main())\r\n File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\__init__.py\", line 545, in script_main\r\n return main(sys.argv[1:])\r\n File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\__init__.py\", line 538, in main\r\n return gyp_main(args)\r\n File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\__init__.py\", line 523, in gyp_main\r\n generator.GenerateOutput(flat_list, targets, data, params)\r\n File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\generator\\msvs.py\", line 2003, in GenerateOutput\r\n sln_projects, project_objects, flat=msvs_version.FlatSolution())\r\n File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\generator\\msvs.py\", line 1762, in _GatherSolutionFolders\r\n return _DictsToFolders('', root, flat)\r\n File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\generator\\msvs.py\", line 1715, in _DictsToFolders\r\n for folder, contents in bucket.iteritems():\r\nAttributeError: 'MSVSProject' object has no attribute 'iteritems'\r\ngyp ERR! configure error \ngyp ERR! stack Error: `gyp` failed with exit code: 1\ngyp ERR! stack at ChildProcess.onCpExit (C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\lib\\configure.js:305:16)\ngyp ERR! stack at emitTwo (events.js:106:13)\ngyp ERR! stack at ChildProcess.emit (events.js:191:7)\ngyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)\ngyp ERR! System Windows_NT 10.0.10586\ngyp ERR! command \"C:\\\\Program Files\\\\nodejs\\\\node.exe\" \"C:\\\\Users\\\\manuel.de.leon\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\yarn\\\\node_modules\\\\node-gyp\\\\bin\\\\node-gyp.js\" \"configure\" \"--fallback-to-build\" \"--module=C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\lib\\\\binding\\\\Release\\\\node-v48-win32-x64\\\\fse.node\" \"--module_name=fse\" \"--module_path=C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\lib\\\\binding\\\\Release\\\\node-v48-win32-x64\"\ngyp ERR! cwd C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\ngyp ERR! node -v v6.7.0\ngyp ERR! node-gyp -v v3.4.0\ngyp ERR! not ok \nnode-pre-gyp ERR! build error \nnode-pre-gyp ERR! stack Error: Failed to execute 'node-gyp.cmd configure --fallback-to-build --module=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node --module_name=fse --module_path=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64' (1)\nnode-pre-gyp ERR! stack at ChildProcess.<anonymous> (C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\node_modules\\node-pre-gyp\\lib\\util\\compile.js:83:29)\nnode-pre-gyp ERR! stack at emitTwo (events.js:106:13)\nnode-pre-gyp ERR! stack at ChildProcess.emit (events.js:191:7)\nnode-pre-gyp ERR! stack at maybeClose (internal/child_process.js:877:16)\nnode-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)\nnode-pre-gyp ERR! System Windows_NT 10.0.10586\nnode-pre-gyp ERR! command \"C:\\\\Program Files\\\\nodejs\\\\node.exe\" \"C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\node_modules\\\\node-pre-gyp\\\\bin\\\\node-pre-gyp\" \"install\" \"--fallback-to-build\"\nnode-pre-gyp ERR! cwd C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\nnode-pre-gyp ERR! node -v v6.7.0\nnode-pre-gyp ERR! node-pre-gyp -v v0.6.29\nnode-pre-gyp ERR! not success Saved lockfile.
Done in 23.66s.
C:\MyFiles\ViewModel\repros\wReact\WReact.xproj(8,3): error MSB4019: The imported project "C:\Program Files\dotnet\sdk\1.0.0-preview3-004056\Extensions\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
Hash: a3af6b1f3df9e38bd254
Version: webpack 1.13.3
Time: 3217ms
Asset Size Chunks Chunk Names
89889688147bd7575d6327160d64e760.svg 109 kB [emitted]
vendor.js 1.48 MB 0 [emitted] vendor
vendor.css 315 kB 0 [emitted] vendor
[0] dll vendor 12 bytes {0} [built]
+ 294 hidden modules
Child extract-text-webpack-plugin:
+ 7 hidden modules
Hash: 4f2367645d019aede5f4
Version: webpack 1.13.3
Time: 4380ms
Asset Size Chunks Chunk Names
main.js 45.4 kB 0 [emitted] main
main.js.map 30.3 kB 0 [emitted] main
+ 16 hidden modules
ERROR in ./ClientApp/components/FetchData.tsx
(16,19): error TS2345: Argument of type '(data: WeatherForecast[]) => void' is not assignable to parameter of type '(value: IResponse) => void | PromiseLike<void>'.
Types of parameters 'data' and 'value' are incompatible.
Type 'IResponse' is not assignable to type 'WeatherForecast[]'.
Property 'length' is missing in type 'IResponse'.
_-----_ ╭───────────────────────╮
| | │ Bye from us! │
|--(o)--| │ Chat soon. │
`---------´ │ Yeoman team │
( _´U`_ ) │ http://yeoman.io │
/___A___\ /╰───────────────────────╯
| ~ |
__'.___.'__
´ ` |° ´ Y `
Activity
MarkPieszak commentedon Nov 22, 2016
Did you install VS2017, it installs .NET Core 1.1 with it, I believe this is part of the problem. Since the projects are still on 1.0.1, since 1.1 was released so recently.
Duplicate of #440 ?
ManuelDeLeon commentedon Nov 22, 2016
I'll try removing .NET Core 1.1 SDK and installing v1.0.1
ManuelDeLeon commentedon Nov 24, 2016
Yep, removing .NET Core 1.1 SDK and installing v1.0.1 fixed it (didn't uninstall VS2017)
MarkPieszak commentedon Nov 25, 2016
The other fix is adding a global.json that tells the project to use your local 1.0.1 copy.
https://github.com/MarkPieszak/aspnetcore-angular2-universal/blob/master/global.json#L3
Glad you got it fixed! @ManuelDeLeon
ManuelDeLeon commentedon Nov 25, 2016
@MarkPieszak
I get the same error when I try to deploy to Azure App Services:
What can I do to deploy it on Azure App Services since it doesn't like the default .xproj?
Edit: Just to be clear, that error is in the Azure logs.
MarkPieszak commentedon Nov 25, 2016
The error came up even after adding a global.json file?
ManuelDeLeon commentedon Nov 25, 2016
I then get "path too long" =/
MarkPieszak commentedon Nov 25, 2016
@SteveSandersonMS Any ideas what could be causing this one, we figured out the 1.1 Core issue, but now he's getting path too long etc when deploying to Azure.
It almost looks like some things didn't get installed properly through npm?
SteveSandersonMS commentedon Nov 25, 2016
Did you remember to specify a Node version for Azure to use via
WEBSITE_NODE_DEFAULT_VERSIONon the Azure management portal? If you don't, it will use NPM 2.x which fails with path-too-long errors. See deployment steps at http://blog.stevensanderson.com/2016/10/04/angular2-template-for-visual-studio/#now-lets-deploy.ManuelDeLeon commentedon Nov 25, 2016
It has the default:
WEBSITE_NODE_DEFAULT_VERSION:4.4.7(trying with 6.7.0)
SteveSandersonMS commentedon Nov 25, 2016
4.4.7 is too old. It includes NPM version 2.15.8. You need NPM >=3.0 for it to work properly on Windows.
Let us know how you go with Node 6.7.0.
ManuelDeLeon commentedon Nov 25, 2016
Different log but it still ends up with "path too long" plus there's
ERROR in Cannot find module 'core-js/library/fn/symbol/iterator'in the middle.SteveSandersonMS commentedon Nov 25, 2016
I'm afraid I don't know why you'd still be getting the path-too-long issue if it's now actually using NPM v3.x during deployment. It makes me suspicious that maybe it's actually still using NPM 2.x. Is there any other evidence in the log to confirm what NPM version it's using?
One bit of good news is that pretty soon, issues like this will no longer be a concern. The templates are changing so that you will no longer need to deploy
package.jsonornode_modulesto production at all. The server-side prerendering feature will be able to run from completely self-contained bundles that never invokerequireat runtime. So, deployments will be much faster, and won't involve NPM at all. This feature should be ready next week.I know that doesn't fix your immediate issue right now (since the new feature hasn't shipped yet). If you're able to repro the deployment issue in a simpler way (e.g., try just deploying a completely empty site that has nothing except your
package.json, and see if Kudu still fails to restore the dependencies even after confirming you're using NPM 3.x), then you might want to report that to the Azure/Kudu teams.MarkPieszak commentedon Nov 27, 2016
Is this a new upcoming feature to azure you're talking about, or to .NET Core and somehow caching node modules you want?
Sounds exciting either way!
ManuelDeLeon commentedon Nov 27, 2016
Can't wait for it. What's the time frame we're talking about here? If it's a few weeks then I'll probably just wait. More than that and I'll probably keep banging my head against the wall.
About my issue, it's definitely using a new node/npm (confirmed via Azure's command line):
But I'm still getting these two errors:
and further down:
Are either of these due to JS Services configuration? If not, how can I contact the Azure or Kudu people?
Thanks for all the help.
ManuelDeLeon commentedon Nov 27, 2016
Interesting, the babel-preset-es2015 folder is empty:
Maybe it's a problem with the es2015 preset version. I'll keep looking.
ManuelDeLeon commentedon Nov 28, 2016
I'm very sorry for the trouble. As it turns out updating the node version in Azure still leaves all the deeply nested files in node_modules. It works correctly if you use a new app service and create the global.json file + set the node version from the get go. In my case I didn't know how to reset it so I had to delete the app and create it again.
Thank you for your patience.
MarkPieszak commentedon Nov 28, 2016
Oh great so, just for clarity if anyone else runs into it:
Glad you got it working!
SteveSandersonMS commentedon Nov 28, 2016
@MarkPieszak:
It's just a change to the default Webpack config that prepares a completely standalone server-side prerendering bundle (like how the client-side bundle is completely self-contained). This means that at runtime, it never calls Node's
requireto load anything fromnode_modules, so you don't even have to deploy that dir to production.We need this because (1) people continue to struggle with deploying
node_modulescorrectly, especially because of NPM 2.x issues on Windows, and (2) publishing from VS is epically slow if you include 20,000+ files fromnode_modules. This change will mean you only have 1 or 2 (large).jsfiles that contain everything needed for server-side prerendering, so publishing/deployment will be just as quick and risk-free as with any other ASP.NET site.MarkPieszak commentedon Nov 28, 2016
I love it, that's a great idea. Yeah it seems to be a reoccurring issue :)
SteveSandersonMS commentedon Nov 28, 2016
That feature is published now (get the latest
generator-aspnetcore-spaversion 0.6.1 to see it - notice thatdotnet publishwon't emit anode_modulesdir any more, yet it still works). Let me know if you can think of any issues with this!MarkPieszak commentedon Nov 28, 2016
Will do, thanks again Steve!