Skip to content

Conversation

@ExposedCat
Copy link

Overview

Currently, only unique-name.content can be used for naming content scripts. This results in inconvenient sorting in IDEs, such as:

- entrypoints
  - google.content
  - popup
  - safari.content

This PR allows to use content.unique-name format, so we would have

- entrypoints
  - content.google
  - content.safari
  - popup

which essentially groups content scripts in places such as IDE file viewers

Manual Testing

Create any content script at entrypoints/content.name/index.ts or entrypoints/content.name.ts

Related Issue

N/A

This PR closes #2043

@netlify
Copy link

netlify bot commented Jan 24, 2026

Deploy Preview for creative-fairy-df92c4 ready!

Name Link
🔨 Latest commit 6c4ab25
🔍 Latest deploy log https://app.netlify.com/projects/creative-fairy-df92c4/deploys/697513cb271d06000805f2bd
😎 Deploy Preview https://deploy-preview-2053--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.

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.

Allow postfix content script names for better sorting

1 participant