How to know when ES modules are done ~ James Burke
There are few pieces of a module system that need to be available for it to be fully functional. I will describe them here and talk a bit about where ECMAScript (ES) modules seem to be at the moment, from an outside public perspective. I am not on TC-39, the committee that works on the ES language specification (otherwise known as JavaScript, JS). Just someone who has worked on a few JS module sys
RequireJS 2.1.11 Released ~ James Burke
RequireJS 2.1.11 is available. Some bug fixes, with the most notable addition is an optimizer option, wrapShim. This will wrap shimmed dependencies in a define() call so that they work better after a build when their upstream dependencies are also AMD modules with dependencies. The most notable case is probably when using an AMD-aware version of Backbone, but using shim config for scripts that dep
RequireJS 2.1.10 Released ~ James Burke
RequireJS 2.1.10 is available. Mainly a maintenance release, and improves some cases when reusing code that was installed via npm. There are two new config options for the loader too: nodeIdCompat: some node modules installed by npm use module IDs like example.js and example interchangeably. Setting this config option to true will accommodate that style. almond 0.2.9+ also supports this option. bu
RequireJS 2.1.9 Released ~ James Burke
RequireJS 2.1.9 is available. Mainly a maintenance release to fix bugs. There is a new skipDataMain option in require.js to avoid the data-main work, which can be useful for browser extensions that should let the main content page's requirejs handle the data-main. Full list of changes: Fixed require.js issues Fixed r.js optimizer issues
RequireJS 2.1.7 Released ~ James Burke
RequireJS 2.1.7 is available. The main changes for this release: For xpcshell, the optimizer uses the built in Reflect parser API instead of Esprima. xpcshell, on Linux and Windows in particular, has a constrained stack, and normal Esprima use was not possible. To accommodate this change, some of the parsing approaches used internally by r.js moved away from token scanning to tree walking. The onl
RequireJS 2.1.6 Released ~ James Burke
RequireJS 2.1.6 is available. Source map support has been expanded. Previously, it was just supported for going from minified, bundled code to the unminified, bundled code. If optimize: 'uglify2' is used, it will now go back to the separated, unbundled files. Source map support is still considered experimental though, so you may find bugs. If you find one, file an r.js issue, ideally with a test c
RequireJS 2.1.5 Released ~ James Burke
RequireJS 2.1.5 is available. Biggest change is support for running the optimizer and loading AMD modules in xpcshell. It is a bit tricky to get xpcshell on your machine. It normally means creating a debug build of Firefox. But if you have a build or test environment built around xpcshell, RequireJS and the optimizer now run in that environment. I tried to get r.js to work in Windows Script Host,
Referencing JavaScript ~ James Burke
Referencing JavaScript. How should it be done? Is there an approach that works for module systems, package managers and project layouts? The following describes the approach in use by AMD/RequireJS and volo, but parts are found in other places like Node, CommonJS and Dojo. The following approach works well for browser-based, web development. Since browser-based development is the harder environmen
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
RequireJS 2.1.12 Released ~ James Burke
Module Frontiers
volo 0.3.0 released ~ James Burke
RequireJS 2.1.4 Released ~ James Burke
RequireJS 2.1.2 Released ~ James Burke
RequireJS 2.1.1 Released ~ James Burke
RequireJS 2.1 Released ~ James Burke