feat: vscode developer environment #24
Conversation
Problem: installing npm directly on the system is not ideal Solution: provide a VSCode developer environment that provisions npm with the latest container. The npm install (and development) will only work given the individual developer has access to the hmxlabs private repositories within the package json file. Signed-off-by: vsoch <vsoch@users.noreply.github.com>
@walaamedhat can you take a look please? There shouldn't be any private HMx packages or code that this depends on? @vsoch feel free to raise a PR with the changes to the JSON files to add the details for flux without running / building locally in the meantime and we will merge/ sort it out |
Working on that now! |
|
I believe it's this one here: Line 8 in dde60e1 |
aah.. yea @walaamedhat this should be in the higher level -ui repo... might have to think about how this is structured for that to be the case. |
2 participants
Problem: installing npm directly on the system is not ideal Solution: provide a VSCode developer environment that provisions npm with the latest container. The npm install (and development) will only work given the individual developer has access to the hmxlabs private repositories within the package json file.
@hamza-x I can't build/run anything, but I'll still give a shot at adding Flux metadata in another PR. If the components don't have anything that warrants private I would make them public, or you can give me access to just build one off, or I can fall back to contributing without testing/running anything.