I'm wondering if there's something we can change here to make the build/release more compatible with VSTS.
I'm simply pulling the GIT, "dotnet restore", "dotnet publish c -release", then copying my files to the artifacts folder. This automatically runs "npm install" as specified in the project.json.
Problem is, in VSTS, we need to bring the node_modules folder along during this step because we don't have a moment during the RELEASE step to rerun npm install again. It will end up including dev dependencies, but i can live with that.
When I copy all the files out of my publish directory, i noticed that "node_modules" was missing. When I run "dotnet publish" without the -c release parameter, it includes the node_modules. I don't think this is something configurable, at least, I don't know where to config it.
To counteract this, i'm grabbing the /node_modules/ folder that is produced by the dotnet publish (a few levels up from the publish folder).
Is there a better way to configure this?
I'm wondering if there's something we can change here to make the build/release more compatible with VSTS.
I'm simply pulling the GIT, "dotnet restore", "dotnet publish c -release", then copying my files to the artifacts folder. This automatically runs "npm install" as specified in the project.json.
Problem is, in VSTS, we need to bring the node_modules folder along during this step because we don't have a moment during the RELEASE step to rerun npm install again. It will end up including dev dependencies, but i can live with that.
When I copy all the files out of my publish directory, i noticed that "node_modules" was missing. When I run "dotnet publish" without the -c release parameter, it includes the node_modules. I don't think this is something configurable, at least, I don't know where to config it.
To counteract this, i'm grabbing the /node_modules/ folder that is produced by the dotnet publish (a few levels up from the publish folder).
Is there a better way to configure this?