Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Unified Diff: README.md

Issue 29705690: Issue 6310 - Start using JavaScript modularization tool (Closed)
Patch Set: Created Feb. 22, 2018, 5:22 p.m.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: README.md
===================================================================
--- a/README.md
+++ b/README.md
@@ -25,16 +25,20 @@
* `i18n.js`: Localization functions, should be included by all pages.
* `messageResponder.js`: Script to be used on the background page to respond
to messages sent by UI code.
* `background.html`, `background.js`: Test implementation of the background
page, should *not be imported*.
* `desktop-options.html`, `desktop-options.js`: Options page, see below
* `subscriptions.xml`: Test subscription data, should *not be imported*
* `polyfill.js`: Browser API polyfills, should *not be imported*
+* `js` directory: new CommonJS modules/entry-points bundled to produce
+ top level pages. As example, `js/desktop-options.js` produces
+ `./desktop-options.js` [IIFE](https://developer.mozilla.org/en-US/docs/Glossary/IIFE)
+ deployed within the extension.
* `lib` directory: Modules to be used on the background page to expose
UI-related functionality.
* `locale` directory: Localized strings, with one directory per locale. The
Firefox format for locale identifiers is used (xx-YY where xx is the language
code and YY the optional region code). The localization strings themselves are
stored in the JSON format, like the one used by Chrome extensions. There is
one JSON file per HTML page, file names of HTML page and JSON file should
match.

Powered by Google App Engine
This is Rietveld