Skip to content

Packages with the same names leads to undefined behavior #277

Open
@theKashey

Description

Title Description
Version 0.24.5
Type feature Request
node 12.16.3
Operating System OSX
Short Description in short - there is a foot gun
Detailed description ....

When new packages are created via copy-paste it is possible to forget to rename a package, having as a result a few ones named in the same way.
This lead to some issue at the linking stage, when some packages would not be linked together. In my case, having 3 similar packages, I have a problem with only one package not linked into the middle of my duplicates.

I know that the root cause sounds a bit stupid. It is. But it's really easy to run into it, and I've spent 4 hours 😅 not able to start my project (and discover the real problem) or commit it due to linting issues (using of unresolved dependency).

Expected solution:

Bolt should throw an error if two packages of a same name were found.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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