fix lint errors in js pipeline

[prathikr]

• suppresses errors related to uncessary type assertions only where it is creating noise for the pipelines
• resolves [baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D by running the recommended update

[fs-eire]

I think this is incorrectly setup. without any of the change in this PR, the npm run lint under folder /js/ does not report any problem. (this is performed in the web CI pipeline)

I think the lint CI pipeline does not respect the typescript project file so that it generates the wrong result.

[prathikr]

I think this is incorrectly setup. without any of the change in this PR, the npm run lint under folder /js/ does not report any problem. (this is performed in the web CI pipeline)

I think the lint CI pipeline does not respect the typescript project file so that it generates the wrong result.

I can repro the issue locally...

[fs-eire]

do you still see the error when doing this:

• run npm ci in /js/
• run npm ci in /js/common/
• run npm ci in /js/web/
• run npm run lint in /js/

[prathikr]

do you still see the error when doing this:

• run npm ci in /js/
• run npm ci in /js/common/
• run npm ci in /js/web/
• run npm run lint in /js/

No, now there is no error. Is this what should be done in the pipeline?

[fs-eire]

I think we can probably ignore the /js/ folder in the Lint, since it is already covered in the Web CI pipeline

[prathikr]

Looks like the lint javascript job only operates on the /js/ folder, should we just remove this stage entirely? link

[prathikr]

Continued in #26984