3

I have a large NX monorepo project containing two distinct applications and hundreds of libs. One of the applications is the main application being developed, the other is a small playground for our own internal UI component library.

In Angular 12 I could serve both of my applications simultaneously, and hit both of them in the browser at the same time. The main application is accessed at 'localhost', the playground application was accessed at the URL 'localhost/component-guide'. The build command for the playground app used --base-href=lib-playground in the command specified in package.json.

Now I have upgraded to Angular 13, and the Angular CLI has removed the --base-href option, so I can no longer pass this on the command line.

I have tried using instead "baseHref": "lib-playground" in the builder in angular.json, as well as in the application's project.json file - neither of these options has worked.

I can understand that --base-href needed to be removed from the CLI, but why does this not have a direct replacement that allowed the same functionality?

I've also tried using serve-path=lib-playground in the package.json - this appeared to have no affect at all.

I've raised an issue in the Angular CLI repo, but it is about to be closed as I have not specified a minimal reproduction, but there is no minimal reproduction, my project is enormous and contains multiple applications that both need to be served and accessed in the browser at the same time. It is not a trivial application.

danwellman
  • 9,068
  • 8
  • 60
  • 88
  • Did you get anywhere with this? I have upgraded our app from Angular 10 to Angular 13. In my angular.json I have "baseHref": "/web/" and that doesn't seem to work any more? – Richard Shergold Feb 24 '22 at 11:59
  • It required a change to our local containerized environment due to complexity of setup. You might be able to just move the config to your angular.json file, as this was the recommendation – danwellman Feb 25 '22 at 10:35
  • not sure what you mean - I already have the baseHref in angular.json but it seems like its being ignored in Angular 13 whereas in Angular 10 it correctly added the base setting in index.html ? – Richard Shergold Feb 25 '22 at 11:25
  • Oh ok, I was passing the option on the command-line prior to the upgrade - the advice to me was to move it into the angular.json file, but as I say, that actually didn't work for us – danwellman Feb 25 '22 at 13:06

1 Answers1

1

We were running into something like this. We discovered that running the ngx upgrade commands as specified in update.angular.io actually changed deployUrl to baseHref in angular.json - however, these are BOTH still valid options to have.

We resolved the issue by setting deployUrl to "pkg/wp" (same location as the outputPath) and setting baseHref to "/" in angular.json. After doing this, everything worked as it did before the upgrade from Angular 10 to Angular 13.

Chris Anderson
  • 666
  • 3
  • 4