fix: build builder and schematics for o3r lib

[vscaiceanu-1a]

Proposed change

Related issues

• 🐛 Fix resolves [Bug]: TS issues in generated file libs/library/schematics/ng-add/index.ts #2714
• 🐛 Fix resolves [Bug]: missing cpy script in file libs/library/package.json #2715

[nx-cloud]

View your CI Pipeline Execution ↗ for commit cabfaae.

Command	Status	Duration	Result
nx run-many --target=test-int	✅ Succeeded	31m 20s	View ↗
nx run-many --target=build --projects=eslint-pl...	✅ Succeeded	1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-01-28 22:45:12 UTC

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.32%. Comparing base (beda44b) to head (cabfaae).
Report is 7 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kpanot]

should not be instead something like:

Suggested change

	const tsConfigPath = '/tsconfig.json';
	const tsConfigPath =['/tsconfig.lib.json', '/tsconfig.app.json', '/tsconfig.json'].filter((file) => tree.exists(file));

and run on all the file found?

[vscaiceanu-1a]

this is only about the root tsconfig file so there won't be app/lib ones

[vscaiceanu-1a]

waiting for #2648 to be merged and to adapt this PR

[vscaiceanu-1a]

as discussed offline, we would want to target the root tsconfig.json

[cpaulve-1A]

Why do we need to update their tsconfig?

[vscaiceanu-1a]

Because this is where the compilerOptions that are incompatible with our project are generated.
To avoid any confusion it is best to update them at the root rather than to add them in the tsconfig.build.json which is expanding the root one.

In this particular case, we are removing noPropertyAccessFromIndexSignature because of some lint issues.