Routing not working in a new window for deployed project

351 Views Asked by At

Currently working on a project where a component has to be opened in a new browser window to display some data.

When we run the code locally, as well as when doing a build with simple parameters, the tab seems to load just fine, and we can view the data required. But whenever we run the code off of our release build parameters, the new window seems to become completely disconnected from the code, not even the base HTML loading in.

The parameters for the local build that works are as follows:

"vendorChunk": true,
"extractLicenses": false,
"buildOptimizer": false,
"sourceMap": true,
"optimization": false,
"namedChunks": true

The parameters for the release build are as follows

"fileReplacements":  [
  {
    "replace": "src/environments/environment.ts"
    "with": "src/environments/environment.prod.ts"
  }
],
"optimization": {
  "scripts": true,
  "styles": {
     "minify": true,
     "inlineCritical": false
  },
  "fonts": {
    "inline": true
  }
},
"outputHashing": "all",
"sourceMap": false,
"namedChunks": false,
"extractLicenses": true,
"vendorChunk": false,
"buildOptimizer": true,
"baseHref": ".",
"budgets": [
  {
    "type": "initial",
    "maximumWarning": "10mb",
    "maximumError": "20mb"
  },
  {
    "type": "anyComponentStyle",
    "maximumWarning": "6kb"
  }
]

Any ideas on which parameters on the release build might be causing the routing to lose the codebase?

0

There are 0 best solutions below