Assets
Currently, it is not possible to import
Assetsas an ES6 module. Any of theAssetsmethods below can simply be called directly in any Meteor server code.
Assets allows server code in a Meteor application to access static server
assets, which are located in the private subdirectory of an application’s
tree. Assets are not processed as source files and are copied directly
into your application’s bundle.
Retrieve the contents of the static server asset as a UTF8-encoded string.
Arguments
- assetPath String
-
The path of the asset, relative to the application's
privatesubdirectory. - asyncCallback Function
-
Optional callback, which is called asynchronously with the error or result after the function is complete. If not provided, the function runs synchronously.
Retrieve the contents of the static server asset as an EJSON Binary.
Arguments
- assetPath String
-
The path of the asset, relative to the application's
privatesubdirectory. - asyncCallback Function
-
Optional callback, which is called asynchronously with the error or result after the function is complete. If not provided, the function runs synchronously.
Get the absolute path to the static server asset. Note that assets are read-only.
Arguments
- assetPath String
-
The path of the asset, relative to the application's
privatesubdirectory.
Static server assets are included by placing them in the application’s private
subdirectory. For example, if an application’s private subdirectory includes a
directory called nested with a file called data.txt inside it, then server
code can read data.txt by running:
const data = Assets.getText('nested/data.txt');
Note: Packages can only access their own assets. If you need to read the assets of a different package, or of the enclosing app, you need to get a reference to that package’s Assets object.