Skip to content

Should add official angular tools/libs to get Angular Environment Variables from Vercel Environment Variables #28381

Closed

Description

@trinm90

Which @angular/* package(s) are relevant/related to the feature request?

common

Description

I use Angular Environment Variables from environment.ts file. Everything is OK on my dev environment. But when I deploy my project to Vercel & need to use Vercel Environment Variables, I have to do an extra step of installing dotenv and creating the set-env.js file : link to the file

Proposed solution

Can Angular team please create an official tool or lib to get the Environment Variables that works with Vercel Environment Variables?

Alternatives considered

Manually creating the set-env.js or config.js to convert Vercel Environment Variables to Angular Environment Variables in environment.ts file : link to the file

Activity

  1. modified the milestone: needsTriage on Sep 9, 2024
  2. transferred this issue fromangular/angularon Sep 9, 2024
  3. alan-agius4 commented on Sep 9, 2024

    @alan-agius4
    Collaborator

    This should be solved in v19 which is currently in prerelease via #28362

  4. trinm90 commented on Sep 22, 2024

    @trinm90
    Author

    This should be solved in v19 which is currently in prerelease via #28362

    If I remember correctly, v19 is not a Long-term support version, but v20 will be. Have Angular team specify a release day for v20?

  5. JoostK commented on Sep 22, 2024

    @JoostK
    Member

    This should be solved in v19 which is currently in prerelease via #28362

    If I remember correctly, v19 is not a Long-term support version, but v20 will be. Have Angular team specify a release day for v20?

    That would be Node's support policy, not Angular's. All Angular majors are supported for ~1.5 years, per https://angular.dev/reference/releases#support-policy-and-schedule

  6. angular-automatic-lock-bot commented on Oct 23, 2024

    @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.

  7. locked and limited conversation to collaborators on Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions