You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: markdown/docs/addon-author-guide.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -295,7 +295,7 @@ The `tree` is the additional fastboot asset that gets generated and contains the
295
295
If your addon requires browser-specific or Node-specific initialization
296
296
code to be run, you would need to define them seperately as follows:
297
297
298
-
1. Browser-Only initializers
298
+
###Browser-Only initializers
299
299
300
300
You should define an initializer under `app/initializers` or `app/instance-initializers` as normally
301
301
you would do. The only addition would to wrap the initializer with a FastBoot environment check. This is
@@ -314,7 +314,7 @@ export default {
314
314
}
315
315
```
316
316
317
-
2. Node-Only initializer
317
+
###Node-Only initializer
318
318
319
319
Often you want to define Node specific behavior for your app at boot time. You should define the Node-Only
320
320
initializer under `fastboot/initializers` or `fastboot/instance-initializers`. Note the `fastboot` directory is a sibling of the `app` or `addon` directory. The FastBoot addon (`ember-cli-fastboot`) will read the `fastboot`
0 commit comments