Requirejs relative paths

[famous]

Requirejs relative paths

[marcvdm]

after allot of searching online i found that you can set the path to famous in the require config. so this actually fixes my problem.

require.config({
    paths: {
        famous: './vendor/famous'
    }
});

But maybe it's still better for dependencies to load relatively from the file that is requiring the dependency

[MylesBorins]

Marc. If you take a look at our yeoman generator you will see that we use a
require js config to put all required vendor code I'm a specific file. We
also use a grunt task to automatically add paths to any bower installed
vendor libs
On Apr 20, 2014 4:10 AM, "Marc van der Meulen" [email protected]
wrote:

after allot of searching online i found that you can set the path to
famous in the require config. so this actually fixes my problem.

require.config({
paths: {
famous: './vendor/famous'
}});

But maybe it's still better for dependencies to load relatively from the
file that is requiring the dependency

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-40892708
.

[MylesBorins]

@marcvdm I'm going to close this issue for right now but feel free to keep the discussion happening.

Part of the architectural decision here regarding non relative paths is that the library is going to eventually be modularized and deployed via a custom package manager. I highly suggest taking a look at the yeoman generator as a way to start famous projects, although I completely understand if you think that tool chain is not for you.