Commit 9233caf

authored

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.

1 parent 1959131 commit 9233cafCopy full SHA for 9233caf

File tree

1 file changed

-1

lines changed

docusaurus/docs
- using-the-public-folder.md

1 file changed

-1

lines changed

`‎docusaurus/docs/using-the-public-folder.md‎`

Lines 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

Comments

(0)

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit 9233caf

File tree

1 file changed

1 file changed

`‎docusaurus/docs/using-the-public-folder.md‎`

0 commit comments