Paths ending on a slash do not work in 'paths' config option

[hay]

Consider a key in a paths configuration like this:

require({
    paths : {
        "foo/" : "bar/"
    }
});

The trailing slash in foo/ seems to cause problems. The require statements using this path down the line don't use the rewritten path. Doing something like:

require({
    paths : {
        "foo/foo" : "bar/bar"/
    }
});

Does work.

I made a small test case here

[jrburke]

I'm thinking of just generating a useful error in this case. Although, what do you expect of these two mappings, do you think they mean the same thing?

require({
    paths: {
        "foo/": "bar/",
        "foo": "bar"
});

What is your expectation for "foo/" vs. "foo", do they mean the same thing to you, or were you trying to express something else?

[hay]

Yes, an error seems to be the most useful solution here.