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.
Latest version doesn't run in development mode #729
Description
I just updated to the latest version 0.8.6 and when I run yo aspnetcore-spa to generate a new project using React I cannot run in debug mode. This seems to be an error with a isomorphic-fetch and typescript. This may be due to the upgrade to the new typescript version. Not sure if there's anything you can do or another package has to be updated.
Activity
bmeverett commentedon Mar 2, 2017
Maybe similar to #725
SteveSandersonMS commentedon Mar 7, 2017
Is this still valid? I just tried it and it worked fine. Do you have repro steps? You might need to make sure you've cleaned your NPM/Yarn cach dirs if you're still getting older packages.
I'll close this because (as mentioned) it does appear to work fine with current packages. If you can describe how to reproduce the issue on a clean machine, please let us know!
bmeverett commentedon Mar 7, 2017
I get this trying to create a new project
yarn 0.21.3
aspnetcore-spa 0.8.6
and selecting the react project. When yo goes to run webpack it shows the conflict types in the screenshot.
When I run directly from the repo templates/reactspa everything runs correctly. Is the yo package not updated?
SteveSandersonMS commentedon Mar 7, 2017
Maybe
yarn cache cleanis somehow not enough to ensure you're getting the latest packages. Have you tried runningyarn upgradeon the generated project, before runningwebpack --config webpack.config.vendor.jsandwebpack?SteveSandersonMS commentedon Mar 7, 2017
If that doesn't work, also check that the
tsconfig.jsonandpackage.jsonfiles in your generated project are the same as in thetemplates/ReactSpaproject that works for you. If there's some discrepancy, it might indicate the problem (and would imply you don't have the latestgenerator-aspnetcore-spa).bmeverett commentedon Mar 7, 2017
yarn upgradeandwebpack --config webpack.config.vendor.jsdid it! Still get the error when creating new projects but that is probably an issue on my end. At least I know how to fix itbmeverett commentedon Mar 7, 2017
I may have spoke too soon.
webpack --config webpack.config.vendor.jsworked but running webpack afterward still produced the same errors