Skip to content

Bug: Warn/Fail if mainConfigFile did not provide any valid RequireJS config #675

@is-already-taken

Description

@is-already-taken

r.js should fail or at least warn if no configuration object could be found when passing the mainConfigFile option.

Current:

At the moment r.js continues at best will producing errors since it's not aware of some configurations that are necessary to build the application.

Goal:

If the option mainConfigFile was provided and no config object can be found, then warn/fail.

Related:

Related issue that describes a possible cause: grunt-requirejs #78 (to understand the use-case) or #406 (my commend in end April 2014).

Related to RequireJS 2.1.11

I'm open for tips and comments.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions