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
Update public folder usage docs to clarify globals (#8299)
Added the relevant topic linked directly, instead of saying it's just in the next section.
Adjusted the text so it sounds more like a recommendation rather than a requirement.
The topic linked is basically explainer to how you'd reference it using the global window object and ways to avoid linter errors. Thus I used 'reference' to give users a hint of what it the linked page would be for.
Copy file name to clipboardExpand all lines: docusaurus/docs/using-the-public-folder.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -63,4 +63,4 @@ The `public` folder is useful as a workaround for a number of less common cases:
63
63
- You want to include a small script like [`pace.js`](https://github.hubspot.com/pace/docs/welcome/) outside of the bundled code.
64
64
- Some library may be incompatible with Webpack and you have no other option but to include it as a `<script>` tag.
65
65
66
-
Note that if you add a `<script>` that declares global variables, you also need to read the next section on using them.
66
+
Note that if you add a `<script>` that declares global variables, you should read the topic [Using Global Variables](using-global-variables.md) in the next section which explains how to reference them.
0 commit comments