Request for Environment support during AfterCompile

Open
#2,265 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, typescript
Domain
build-system, tooling

Research direction

Start by reviewing the default AfterCompile target and how Environment and EnvironmentVariables are handled in the project XML. Reproduce the Vue TypeScript template case, comparing debugging with a project-only build; done means process.env.VUE_APP_VALUE values are present in the build artifact.

Written by the indexing model from the issue text.

Description

Are there plans to support the Environment property while the default AfterCompile target runs?

Our project started with the Vue typescript template. It's possible right now to make multiple properties manually in the XML for each configuration, but any process.env.VUE_APP_VALUEs are only available when debugging. If the project is only built, they are absent from the build artifact. is automatically upgraded by Visual Studio to when reloading the project. Our team is using env-cmd and a custom start script and AfterCompile target for now.

I am not familiar with msbuild to begin with, so this could a simple mistake!

Dominant language
C#
Stars
1.8k
Forks
355
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/nodejstools

All issues in microsoft/nodejstools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.