Question about Chrome Extension file naming and source maps

[Jagadeesh Ch]

Question about Chrome Extension file naming and source maps

Hi everyone,

I'm preparing my Chrome extension for submission to the Chrome Web Store and have two questions about best practices:

1. File naming convention:
Instead of using standard file names like content.js and background.js, would it be acceptable to use randomized character-based file names such as:

dff2c7yhpl0izck.js
hdmv4gf0o9lkd.js

Are there any Chrome Web Store policies or technical issues that would prevent this approach?

2. Source map configuration:
Is it safe to use devtool: false in my webpack configuration to prevent source maps from being generated, or could this cause issues during the Chrome Web Store review process?

I want to make sure my extension follows all guidelines while maintaining a professional build setup.

Thanks for any insights you can share!

[Oliver Dunk]

Hi Jagadeesh,

Using randomized file names and turning off sourcemaps are both ok.

The relevant policy here is our Code Readability Requirements: https://developer.chrome.com/docs/webstore/program-policies/policies#code_readability_requirements. I would consider both of these to fall under minification which is a common practice in the store and something our team is prepared to handle.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/f7949460-409b-47e1-bcf7-40d53698f512n%40chromium.org.