[Ignore ref tags in yaml Typescript Generator] Unable to load RELATIVE ref

We have a requirement to generate Angular services and models using the same OpenAPI YAML that we are using to generate Implementation interfaces, request and response objects on the Java side. Below is an example of such YAML. There is no problem in client generation on both Java and Angular side but just on the Angular repository we don't want to generate models for some of the response types. Ex- for 500, 503 and 400 response codes.
Reason for that is we do not have access to error-response.yml on Angular side. So we just want to ignore client generation for response codes 500, 503, and 400.
Please let me know if there a way of doing so in typescript?

/document/upload:
post:
summary: Uploads Document for sysdocs
operationId: uploadSysdoc
tags:
- documents
requestBody:
content:
multipart/form-data: # Media type
schema: # Request payload
$ref: '../schemas/document.yml#/components/schemas/SysdocFileUpload'
parameters:
- name: fileTypeEnum
in: query
x-constraints: "@NotNull(message = "{fileupload.file.type.required}")"
schema:
{ $ref: '../schemas/document.yml#/components/schemas/FileType' }
required: true
responses:
'200':
$ref: '../schemas/maintenance.yml#/components/responses/uploadResponse'
'500':
$ref: "../commons/error-response.yml#/components/responses/internalError"
'503':
$ref: "../commons/error-response.yml#/components/responses/serviceUnavailable"
'400':
$ref: "../commons/error-response.yml#/components/responses/badRequest"

Start with the OpenAPI YAML example, especially the response references for 500, 503, and 400 and the relative error-response.yml path. Trace how TypeScript/Angular generation handles those response references and determine how they could be excluded without affecting the 200 response. Done means the requested responses are omitted while the remaining client models and services still generate successfully.