Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

optimizer ignores baseUrl when run from different directory #768

Closed
jwbay opened this issue Jan 12, 2015 · 0 comments
Closed

optimizer ignores baseUrl when run from different directory #768

jwbay opened this issue Jan 12, 2015 · 0 comments

Comments

@jwbay
Copy link

jwbay commented Jan 12, 2015

It seems r.js is overriding baseUrl with the directory it's run from when doing single-file optimization with main and out. I've got a stripped-down reproduction repo located here with notes.

Given a project like this:

/app
  |- main.js - application entry point
/configs
  |- build-config.js - r.js build configuration
  |- require-config.js - shared configuration between runtime and build
/libs
  |- jquery.js
/bin

Running the optimizer from a subdirectory like bin/ with r.js.cmd -o ../configs/build-config.js makes r.js try to resolve module locations relative to the working directory, bin/, instead of the provided baseUrl of ../, or the project root.

Any help is appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant