resolving file's relative parent path during optimization

[jmonma]

I am able to build just fine when referencing css files that are children of the current directory (i.e. css!css/core). However, If I try to access a css folder that's a child of the parent directory it fails (i.e. css!../css/core).

My current setup:
/MyApp/css
/MyApp/css/core.css
/MyApp/js
/MyApp/js/example.js

When I try to build referencing a css file, it ends up resolving the url to the actual location of the plugin. So when I try to build referencing 'css!../css/core' from example.js, instead of resolving to /MyApp/css/core.css it resolves to /MyApp/js/lib/require/plugins/require-css/css/core.css and fails because that file does not exist.

Any thoughts on why this might be happening? I've tried it with my baseUrl at both /MyApp (css!css/core.css) and at /MyApp/js (css!../css/core.css) and both tried to resolve to the plugin folder instead of the actual file.

[guybedford]

I see what the problem is here, working on a fix and will report back soon.

[guybedford]

I've included a fix in the master branch, let me know if this works for you.

[jmonma]

This fixed the issue. Thanks for the rapid response!