microsoft / microsoft/nodejstools
Request for Environment support during AfterCompile
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.8k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
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!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100