mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
# Assets
|
|
|
|
> Currently, it is not possible to import `Assets` as an ES6 module. Any of the `Assets` methods 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.
|
|
|
|
<ApiBox name="Assets.getTextAsync"/>
|
|
<ApiBox name="Assets.getBinaryAsync"/>
|
|
<ApiBox name="Assets.absoluteFilePath"/>
|
|
|
|
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:
|
|
|
|
```js
|
|
const data = await Assets.getTextAsync('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.
|