refactor(@angular/ssr): export tokens from the /tokens entry point

[alan-agius4]

This commit relocates the DI tokens to a dedicated entry point. This change ensures that we do not depend on tree-shaking to eliminate server code from client bundles.

Closes #28670

[alan-agius4]

Any other ideas for as an entry-point name?

[dgp1130]

@angular/ssr/tokens seems reasonable to me.

[dgp1130]

Is the goal to support users doing:

import { REQUEST } from '@angular/ssr/tokens';

inject(REQUEST, { optional: true });

And be able to run that on the client without a risk of retaining server code?

I can see some users having encountering friction from having to import the non-default entry point, but IDE auto-imports should mostly solve that problem, and reducing the risk of server code in the client bundle seems worth the trade-off.

[dgp1130]

@angular/ssr/tokens seems reasonable to me.

[alan-agius4]

Is the goal to support users doing:

import { REQUEST } from '@angular/ssr/tokens';

inject(REQUEST, { optional: true });

And be able to run that on the client without a risk of retaining server code?

I can see some users having encountering friction from having to import the non-default entry point, but IDE auto-imports should mostly solve that problem, and reducing the risk of server code in the client bundle seems worth the trade-off.

Correct.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}