1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Anuncie Aqui
    Anuncie aqui você Também: fdantas@4each.com.br

Angular multi-project site with legacy code?

Discussão em 'Angular' iniciado por Alnitak, Setembro 10, 2024.

  1. Alnitak

    Alnitak Guest

    I run a (hobby) site that currently consists of four separate AngularJS applications and some common JS code. The site's code can currently be served as-is as there's no transpiling involved. The main site-wide index.html is not an Angular(JS) app - it's pure HTML. Each app sits in its own subdirectory and has its own index.html too.

    Since AngularJS is now somewhat obsolete I want to start converting some of the common code to TypeScript and also have future new apps use Angular (v18+) instead of AngularJS, perhaps also rewriting some of that legacy code.

    Is there a way to coerce the Angular build system to handle automatic building and bundling of the (mostly static) relevant parts of the old code base, including transpiling where necessary?

    My end goal would be a single dist/ folder that contains the four old projects and any new ones, all ready for upload.

    Continue reading...

Compartilhe esta Página