Jetpack/Release Notes/1.0: Difference between revisions

Jetpack/Release Notes/1.0 (view source)

Revision as of 00:33, 21 June 2011

1,255 bytes added , 21 June 2011

→‎Known Issues

Wbamberg

canmove, Confirmed users

737

edits

@@ Line 77: / Line 77: @@
 See the [https://bugzilla.mozilla.org/buglist.cgi?order=Bug%20Number&bug_status=__open__&product=Add-on%20SDK complete list of known issues and requests for enhancement]. We've listed some of the more important issues separately below.
+'''[https://bugzilla.mozilla.org/show_bug.cgi?id=663480 Bug 663480]'''
+The SDK automatically includes a dependency on the packages supplied with the SDK such as <code>addon-kit</code> and <code>api-utils</code>. This means that you can <code>require()</code> modules in the SDK such as <code>widget</code> and <code>page-mod</code> without having to specify <code>addon-kit</code> as a dependency.
+You can also use modules from other packages, such as the packages listed [https://wiki.mozilla.org/Jetpack/Modules here], by including a reference to the package in your <code>package.json</code> file.
+However, if you do add any dependencies to <code>package.json</code>, then the SDK will no longer add  <code>addon-kit</code> or <code>api-utils</code>  automatically, and you must add them manually if you want to include their modules.
+From dietrich on IRC:
+<dietrich>	packages dir in add-on root should be additive tothe core
+	not replace the core
+	(in terms of absolute dependencies)
+	i guess it's not about the packages dir though
+	<peregrino>	dietrich: yes, but I think that is something not yet fully documented
+<dietrich>	it's the fact that specifying anything in the dependencies field in package.json blows away the default dependendencies
 '''[https://bugzilla.mozilla.org/show_bug.cgi?id=663048 Bug 663048]'''