Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[cli] Options are processed differently if in package.json / command line or passed to atomify() from code #35

Description

@almilo

Because of parseArgs() being just applied from cli.js, if the 'js' config value is a string of the form ':', it will be interpreted correctly only from the command line or the atomify section in package.json. If passed to atomify function, it will throw a 'cannot find module ...' error:

var options = {
js: 'main.js:alias.js'
};
require('atomify')(options);

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions