Consider "Configuration/TSconfig/page.tsconfig"

[mbrodala]

In addition to Configuration/PageTs/main.tsconfig this package should also support Configuration/TSconfig/page.tsconfig. This is one of the options with the most votes in the decision about File Endings for TypoScript and TSconfig files.

Not sure about casing here ...

[josefglatz]

+1 for using `Configuration/TSconfig` as base

[bernhardberger]

I have to remove my +1, didn't read the opening post properly, but I agree with @josefglatz because:

Configuration/TSconfig/Page and Configuration/TSconfig/User are the official conventions.

https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ExtensionArchitecture/FilesAndLocations/Index.html

[kszymukowicz]

I suppose those pathes could be also configurable in site config.

[bmack]

FYI: TYPO3 v12 Core now loads all EXT:my_ext/Configuration/page.tsconfig files by default in v12, not per-site.

Depending on the structure, We could use this as a third check for a file name (if the other files exist). Anyone wants to create a PR?

[infabo]

https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-96614-AutomaticInclusionOfPageTsConfigOfExtensions.html

[sorenmalling]

I've found a need for "site" (pagetree) specific settings, so I auto-include a "site.tsconfig" for each of my site packages.

Since the tsconfig is included on a per pagetree basis (based on the site), could this be a way to do it?