Skip to content

Loading…

make require.config.js filename configurable #73

Open
tbranyen opened this Issue · 0 comments

1 participant

@tbranyen

hard coded filenames can cause undesirable effects, in my case very long deps for my configuration file.

eg:

deps: ["../assets/jam/require.config", "main"]

ideally the package.json for the project would have:

"jam": {
  // Name could be better...
  "configPath": "config.js"
}

which would result in:

deps: ["../assets/jam/config", "main"]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.