You can also import CSS directly from a JavaScript file to control load order if you have the ecmascript package installed:. For example, font-awesome is a very popular font library that provides lots of font-based icons. New icons appear frequently as the library is developed and it would be difficult to manage all the updates if you were to copy the entire font-awesome code base to your own app and git repository.
Instead use the following to include these fonts:. However, compilation of specific npm packages for example, to support older browsers that the package author neglected , can be achieved through the meteor. The keys of the meteor. These strings and arrays of strings have the same meaning as the second argument to api.
The meteor. Recompiled packages must be direct dependencies of the application. Meteor will compile the exposed code as if it was part of your application, using whatever compiler plugins you have installed.
You can influence this compilation using. This will create an npm-shrinkwrap. For even more precision the contents of a given version of a package can change , and to avoid a reliance on the npm server during deployment, you should consider using npm shrinkpack.
Many npm packages rely on an asynchronous, callback or promise-based coding style. For several reasons, Meteor is currently built around a synchronous-looking but still non-blocking style using Fibers. The global Meteor server context and every method and publication initialize a new fiber so that they can run concurrently. Many Meteor APIs, for example collections, rely on running inside a fiber.
This means you need to initialize your own fiber and environment to use asynchronous Node code inside a Meteor app. In most cases, wrapping the callback in Meteor. You can run meteor update without any arguments to update all packages and Meteor itself to their latest versions, or pass a specific package to update just that one, for example meteor update ostrio:flow-router-extra.
If your app is running when you add a new package, Meteor will automatically download it and restart your app for you. You can get more details on all the package commands in the Meteor Command line documentation. Sometimes a package will have no exports and have side effects when included in your app.
For backwards compatibility with Meteor 1. However, it is recommended that you import these symbols first before using them. To get more details on how to determine this see CSS source versus import files. CSS files in an Atmosphere package are declared with api. Typically the package will warn you if you have not done so. Each Atmosphere package that you use in your app exists in its own separate namespace, meaning that it sees only its own global variables and any variables provided by the packages that it specifically uses.
When a top-level variable is defined in a package, it is either declared with local scope or package scope. Notice that this is just the normal JavaScript syntax for declaring a variable that is local or global.
In addition to local scope and package scope, there are also package exports. You can detect if the possibly-present weakly-depended-on package is there by seeing if Package. It's okay to load this dependency after your package. In general, dependencies specified by api. You can use this option to break circular dependencies. Give users of this package access to another package by passing in the string packagename or a collection of packages by passing in an array of strings [ packagename1 , packagename2 ].
Export package-level variables in your package. The specified variables declared without var in the source code will be available to packages that use your package. If your package sets the debugOnly , prodOnly or testOnly options to true when it calls Package. ExportedVariableName to access the value of an exported variable. If you only want to export the object on the server or the client , you can pass in the second argument e.
If you only want to use the file on the server or the client , you can pass this argument e. You can call api. By default, the file will be loaded on both server and client. If this file is JavaScript code or will be compiled into JavaScript code by a build plugin, don't wrap the resulting file in a closure.
Specify asset files for your package. Specify where this asset should be available e. Set up your tests with the Package. The tests will need to depend on the package that you have just created. For example, if your package is the email package, you have to call api. If you used meteor create to set up your package, Meteor will create the required scaffolding in package. A function that takes in the package control 'api' object, which keeps track of dependencies and exports. Specify which NPM packages your Meteor package depends on.
Plugins are installed from plugins. An object where the keys are plugin names and the values are version numbers or GitHub tarball URLs in string form. Define a build plugin. A build plugin extends the build process for apps and packages that use this package. For example, the coffeescript package uses a build plugin to compile CoffeeScript source files into JavaScript. Meteor packages that this plugin uses, independent of the packages specified in api.
The source files that make up the build plugin, independent from api. In some cases we need to offer options in packages where these options are not going to change in runtime.
We prefer to have these options defined in a configuration file instead of using JS code to call specific functions to define options in runtime. For example, in quave:collections package you can force collections to be available only in the server like this:. If it needs to be available in the client follow the same structure inside the public key.
You can use quave:settings package to read options in the format above already merging the private and public options. This way we avoid having to call a specific code before another specific code in a package as the setting is stored in the settings, and the package can load it when necessary instead of relying on a specific order of calls from the developer in the app code. Inside a build plugin source file specified in Package. The file extension that this plugin should handle, without the first dot.
Examples: "coffee" , "coffee. Meteor packages can provide build plugins - programs that integrate with the build tool Isobuild used to compile and bundle your application. Starting with Meteor 1. Here is an overview of operations Isobuild performs on the application and packages source:. Usually build plugins implement a class that is given a list of files to process. Commonly, such files have the following methods:. To register a linter build plugin in your package, you need to do a couple of things in your package.
In your build plugin sources, register a Linter Plugin: provide details such as a name, list of extensions and filenames the plugin will handle and a factory function that returns an instance of a linter class.
0コメント