Skip to content

Symlinked node_modules breaks build on version>1.1.7 #175

Open
@SpencerBriereWEQ

Description

@SpencerBriereWEQ

In version>1.1.7, the behavior of how this plugin handles node_modules seems to have changed.

In our project, we have multiple sub-projects which all share the same dependencies. Rather than having dozens of duplicate node_modules, we opted to symlink a top-level node_modules folder into the sub-projects. Now, rather than symlinking to our symlink, the symlink is copied. This results in a broken symlink as the path doesn't evaluate to the node_modules folder.

Directory structure:

  • package.json
  • node_modules
  • projects/
    • a/
      • node_modules -> ../../node_modules
      • package.json -> ../../package.json
      • .build/
        • node_modules -> ../node_modules // Expected Behavior
    • b/
      • node_modules -> ../../node_modules
      • package.json -> ../../package.json
      • .build/
        • node_modules -> ../../node_modules // Current Behavior - broken symlink

Symlink path: ../../node_modules
Expected Behavior: node_modules -> ../node_modules
Current Behavior: node_modules -> ../../node_modules

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