Files
meteor/docs/client/packages.html
Emily Stark a102872a96 Rework browser-policy to make API more intuitive.
- Remove starter-browser-policy and replace it with
  BrowserPolicy.enableContentSecurityPolicy(), which gives you the starter
  policy and allows you to use the other BrowserPolicy functions to configure
  it. This is motivated by the fact that the API isn't very intuitive without a
  well-defined starting policy. ex: if the package starts off without a policy,
  and then the user calls allowAllContentSameOrigin(), that will result in
  turning off inline scripts, which is probably not what they wanted.
- AllContent functions do more of what you'd expect now;
  i.e. BrowserPolicy.disallowAllContent() actually disallows all content,
  instead of setting default-src to 'none', which will allow other types of
  content that have previously had srcs set for them.
- Add some tests
2013-09-28 18:44:04 -07:00

39 lines
822 B
HTML

<template name="packages">
{{#better_markdown}}
<h1 id="packages">Packages</h1>
Meteor supports a variety of add-on packages and third party
libraries. While you can build great applications using only the Meteor
core functionality, optional packages can make development even faster
and better.
Packages can be added and removed from a Meteor project with:
$ meteor add <package_name>
and removed with:
$ meteor remove <package_name>
{{> pkg_accounts_ui}}
{{> pkg_amplify}}
{{> pkg_appcache}}
{{> pkg_audit_argument_checks}}
{{> pkg_backbone}}
{{> pkg_bootstrap}}
{{> pkg_browser_policy}}
{{> pkg_coffeescript}}
{{> pkg_d3}}
{{> pkg_force_ssl}}
{{> pkg_jquery}}
{{> pkg_less}}
{{> pkg_random}}
{{> pkg_spiderable}}
{{> pkg_stylus}}
{{> pkg_showdown}}
{{> pkg_underscore}}
{{/better_markdown}}
</template>