Skip to content
This repository was archived by the owner on Sep 6, 2021. It is now read-only.

Global RequireJS config paths should be passed to extensions #1087

Closed
jasonsanjose opened this issue Jun 20, 2012 · 1 comment
Closed

Global RequireJS config paths should be passed to extensions #1087

jasonsanjose opened this issue Jun 20, 2012 · 1 comment
Assignees
@jasonsanjose
Labels
code cleanup low priority

Comments

@jasonsanjose
Copy link
Member

To support RequireJS plugins in extensions, the path must be configured for each extension's require context.

Currently we must hardcode the path to a RequireJS extension in 2 places (1) global brackets require and (2) ExtensionLoader require context creation.

Ideally there would be a way to query the global require context and pass the config options to extensions.
@ghost ghost assigned jasonsanjose Jun 20, 2012
@jasonsanjose jasonsanjose mentioned this issue Jun 20, 2012
Merged
@pthiess
Copy link
Contributor

pthiess commented Jun 22, 2012

reviewed - Jason is assigned

petetnt added a commit to petetnt/brackets that referenced this issue Jan 2, 2016
@petetnt
Use the global RequireJS config for ExtensionLoader. Fixes adobe#1087
00767ab
@petetnt petetnt mentioned this issue Jan 2, 2016
Merged
petetnt added a commit to petetnt/brackets that referenced this issue Aug 20, 2016
@petetnt
Use the global RequireJS config for ExtensionLoader. Fixes adobe#1087
fb60e92 
Signed-off-by: petetnt <pete.a.nykanen@gmail.com>
@core-ai-bot core-ai-bot mentioned this issue Aug 29, 2021
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jasonsanjose jasonsanjose

Labels
code cleanup low priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jasonsanjose @pthiess