Sunday, September 9, 2018

Web Devs, Help! How to lay out SignalR + JS Frontend application structure?

Hi, i am in the design process of building a web application with a ASP.NET Core / SignalR backend and a JS frontend.

From tutorials this always revolves around angular... but even when ignoring the ASP.NET Core routing backend... the dotnet new angular template is so goddamn bloated. There's like 9 gazillion nuances of typescript, npm, webpack, babel,... already implied. I'm just starting off. So in my head it seems like a good idea to let JS take control of the whole frontend including the server aka routing. This is where my experience with dotnet doesn't really help me anymore. I am searching for this:

  • TypeScript support:
    • Shouldn't all frameworks support typescript because typescript is just language that compiles to javascript?
  • SignalR Support:
    • SignalR is available as an NPM package, so i assume this shouldn't be an issue
  • Rendering is done on clientside
  • works using npm run

the current design / mockups rely on a SPA - design, so support for that would be A+...

I am fine learning about things like webpack, but not to the extent that before writing any UI code, i have to have 20 different config files aligned.

EDIT: btw i have some JS experience. Mostly some basic stuff and little bit of jquery here and there. I am able to write ajax requests without a framework, but all the ES stuff went over my head in the last ~8 years.

Web Devs, Help! How to lay out SignalR + JS Frontend application structure? Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team