Skip to content

Conversation

@lookfirst
Copy link

Small typo fix

@netlify
Copy link

netlify bot commented Aug 24, 2025

Deploy Preview for creative-fairy-df92c4 ready!

Name Link
🔨 Latest commit 8f36ec9
🔍 Latest deploy log https://app.netlify.com/projects/creative-fairy-df92c4/deploys/68aa7f4dde58450008c9c8b0
😎 Deploy Preview https://deploy-preview-1858--creative-fairy-df92c4.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@aklinker1
Copy link
Member

aklinker1 commented Sep 3, 2025

Could be, but it doesn't have to be. Either name works as an unlisted script.

@aklinker1 aklinker1 closed this Sep 3, 2025
@lookfirst
Copy link
Author

@aklinker1 Where is that documented then? It was a source of confusion for me.

@lookfirst
Copy link
Author

@aklinker1 Thanks, but I don't see where it says "-" vs. "." is ok in the name of the folder. That's where the confusion stems.

@aklinker1
Copy link
Member

aklinker1 commented Sep 3, 2025

@aklinker1 Thanks, but I don't see where it says "-" vs. "." is ok in the name of the folder. That's where the confusion stems.

@lookfirst The docs state that you use injectScript with an unlisted script. Unlisted script paths can look like this:

  • entrypoints/{name}.[jt]sx?
  • entrypoints/{name}/index.[jt]sx?

The {name} can be anything you want. It can include alphanumerics, periods, dashes, other punctuation, etc. It should all work.

.background and .content are the only recognized dot suffixes for JS files, corresponding with background and content script entrypoints. Any other JS file matching the unlisted script path patterns above will be categorized as an unlisted script.

I didn't document what could go in the {name} because it can be anything. Not sure where a good place for that would be, it's true for all types of entrypoints.

@aklinker1
Copy link
Member

You can see the type of entrypoint your files are categorized by running the following and searching your console for "All entrypoints"

wxt prepare --debug

@lookfirst lookfirst deleted the patch-1 branch September 4, 2025 19:53
@lookfirst
Copy link
Author

@aklinker1

I didn't document what could go in the {name} because it can be anything.

The easiest way to avoid any sort of confusion would be to document that {name} can be anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants