Skip to content
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

Closed
bmeverett opened this issue Mar 2, 2017 · 7 comments
Closed

Latest version doesn't run in development mode #729

bmeverett opened this issue Mar 2, 2017 · 7 comments

Comments

@bmeverett
Copy link

bmeverett commented Mar 2, 2017

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.

image

@bmeverett
Copy link
Author

Maybe similar to #725

@SteveSandersonMS
Copy link
Member

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
Copy link
Author

bmeverett commented Mar 7, 2017

I get this trying to create a new project

yarn 0.21.3
aspnetcore-spa 0.8.6

yarn cache clean
yo aspnetcore-spa

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
Copy link
Member

Maybe yarn cache clean is somehow not enough to ensure you're getting the latest packages. Have you tried running yarn upgrade on the generated project, before running webpack --config webpack.config.vendor.js and webpack?

@SteveSandersonMS
Copy link
Member

If that doesn't work, also check that the tsconfig.json and package.json files in your generated project are the same as in the templates/ReactSpa project that works for you. If there's some discrepancy, it might indicate the problem (and would imply you don't have the latest generator-aspnetcore-spa).

@bmeverett
Copy link
Author

yarn upgrade and webpack --config webpack.config.vendor.js did 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 it

@bmeverett
Copy link
Author

I may have spoke too soon. webpack --config webpack.config.vendor.js worked but running webpack afterward still produced the same errors

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants