/
tasks.txt
119 lines (79 loc) · 4.78 KB
/
tasks.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
Next release
--------------
- update to jQuery 1.5.1 when released
- Consider putting in the version detection?
- Move up plugins, or move them to their own repo?
- build tool to rename require and define calls to other names?
- Build the optimizer as its own project, at least enough to take out the
work from jquery-require-sample
- Confirm: From Richard Backhouse: As an FYI I have been doing my own investigation of using UglifyJS for compression
and one thing I found when trying to compress dojo 1.5 code was that I had ensure that "make_seqs"
flag was set to false when calling ast_squeeze. If I left this flag set to true the code would not load.
- localeList for i18n.js support, for better Dojo support.
Bugs to work on
------------------
- Test build scripts on windows.
- plugins in excludeShallow do not work, are not excluded. For example text! one.
- "libs/static.lib.02", //kaaahhhhnnnn!!!
- Build with requireplugins-jquery.js uses bad definition for require/text, probably other plugins. Use a jqueryStub.js
for builds that need it with plain define, and allow the build system to load
the plugins. A problem, since previously built layers with plugins in them
can cause a problem.
- replacement for modify that intercepts callbacks, holds off until another module loads them?
- coffeescript plugin
- Support Node's "extensions" mechanism.
- File bug for UglifyJS on dead code removal.
- Update AMD page to mention require scanning means only do them at the top.
- Consider patches in jetpack for:
- removing scanning
- add amd object
- add plugins?
- building with packages.build.js, the alpha/replace path mapping does not work out?
- build's name insertion if there is comment between define( and the [dependencies]
- ending slash in paths should throw error: https://github.com/jrburke/requirejs/issues/issue/49/
- Document new closure compiler options from neonstalwart
- require.modify alternative syntax/patch.
- has.js plugins
- require.def patch: https://github.com/jrburke/requirejs/pull/50
- Visualization of dependencies, highlighting circular dependencies: RobbertAtWork
- email on jsonp removal, toUrl and package names.
- Nested package config: https://github.com/jrburke/requirejs/pull/28
- IE, on errors, hits script onload, but need to make sure it is treated as a failure?
- https://github.com/jrburke/requirejs/issues#issue/26:
spider: throw with isCheckLoaded: maybe pass for refactor branch?
https://github.com/jrburke/requirejs/issues/issue/9
- Optimizer cannot include order! plugins in a build at the moment.
Optimizer improvements:
2) Investigate the issue with main.js baseUrl overriding the one in app.build.js
4) See if the pathing can be made simpler (abde's comment).
- Figure out if isCheckLoaded can be avoided. Not likely, but revisit.
- Finish PS3 work, investigate test failures, document level of support.
- Check out blackberry emulators at:
https://www.blackberry.com/Downloads/entry.do?code=060AD92489947D410D897474079C1477
- Building a lib that has its own lookup paths, so it can be self-contained?
but what if want to share code? Maybe just make it an option, you can do it,
but lose out on shared common.
- For function(require, exports, module) form, do not pass exports if the function
does not ask for it, to allow the function to set the exported value by returning.
- Figure out why priorityOrder test does not work, and if it should be supported.
Loading a plugin while waiting for a priority load may not be worth supporting,
it also means it will be slower. A priority module can include plugins but just
use a plugin to load the priorit module.
- DOH updates
- get latest code
- fix rendering in IE 9 standards? How to get it to render in IE9 standard mode?
- Allow module names that match Object.prototype method names?
- browser test for loading css?
- Best practices/architecture guide
- consider removing require.isBrowser and require.s.isBrowser, check the tests, and send email to list first.
- Make sure text plugin works offline.
- Get Blackberry simulator. Blackberry greater than 4.6, and particulary with the Blackberry 9500 simulator (with OS v4.7),
install and launch Blackberry MDS service simulator before running simulator to get network.
- trying to find path of the file executed, as given to rhino:
http://groups.google.com/group/jsdoc-2/msg/b1dd2f8991156fa0
- with appName, and no native require, setting path to be outside the baseUrl meant that the require path was really
relative to the output folder name?
- Use JSDoc to document a full module?
- When doing docs via jsdoc, using {some/module} as return types? How does JSDoc deal with the nested objects?
Probably needs custom work to get it recognize the module concept thing.
- To validate with Caja: http://caja.appspot.com/ and paste the code inside a script tag.