Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
This repository was archived by the owner on Apr 8, 2020. It is now read-only.

dotnet publish removes node_nodules - VSTS probs #235

Copy link
Copy link
@alphster

Description

@alphster
Issue body actions

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?

Reactions are currently unavailable

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

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.