Skip to content

relative path will resolve module of same name #13

Description

@louisbuchbinder

Lets say I have a file ./flog.js and am using a module "flog" then the browser directive in my package json mistakes my relative path for the module.

my code

"browser": {
  "./flog": "./other-file"
}

I expect this directive to replace usages of the file ./flog with the file ./other-file, however browserify gets confused with the module named "flog". The two fixes I have found are 1. Use the .js extension to explicitly reference the file ./flog.js or 2. (not really a fix) rename the module to "flogger".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions