Skip to content

Access to unpacked folders with docker-build #16

@AaronBuxbaum

Description

@AaronBuxbaum

Hopefully there's an easy answer to this!

I'm trying to use the docker-build plugin on Yarn 3 -- it works really well, with the exception of one big issue. The workspace in question is a package, which means that it has files defined under package.json. Because of that, yarn pack returns only those files, meaning that I'm unable to do anything outside of manifests and the files in the package itself.

What I'm hoping for is a way to copy in the original code from my workflow; I can make a minimal docker image of dependencies with the excellent existing manifests folder, but I can't do anything that requires the source code, including building and testing. Any advice is appreciated.

--copy seemed like a possible answer here (though I don't think it's how it's intended to work), but that returns an "Invalid filename" error when passed a folder.

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