Closed joelhoisko closed 3 years ago
This may be related to the typescript build stuff we have. It's not anything wrong in the boilerplate itself. Maybe hear with @pavsaund or @smithmx
➤ Einar Ingebrigtsen commented:
Should we promote a developer experience which requires the SPA to not be hosted from the ASP.NET Core Kestrel Web Server. This would then be from a learning perspective and documentation a more modular experience as the backend is then separate. That means that the Boilerplate should be updated with the WebPack DevServer having the proxying enabled to forward our Query/Command posts through that - as we've done for the Banking example: https://github.com/dolittle-samples/Bank/blob/master/Source/Banking/Web/webpack.config.js
Going to locahost:5000/swagger
works normally still, it's just that going to localhost:5000
breaks.
Adding this line to webpack.config.js
before the webpack is called fixes the error, the page is still blank for some other reason but it's at least something.
process.env.DOLITTLE_WEBPACK_OUT = path.resolve("../Core/wwwroot/");
Probably has something to do with this line? Not sure where to fix this problem, we could do it dirty and just change the webpack.config.js boilerplate but that doesn't seem quite correct.
Using yarn start
seems to be better in the way that it actually shows you the aurelia errors you're getting in the console. Using yarn build
with the Core/wwwroot/
path set doesn't show errors in aurelia, making debugging really hard.
Env:
I'm creating a blank new dolittle application and bounded context using the CLI and I'm trying to run it.
I build the frontend first (after having fixed the capitalization). Then I run the backend from the Core folder using
dotnet run
and it runs.But when I go to localhost:5000 I get greeted with this error both in the browser and the terminal:
Probably linked to the boilerplates for C#.
┆Issue is synchronized with this Asana task