Portal deploys now read ee.jsonc files with comments and trailing commas

If your site has an ee.jsonc file, a deploy from the portal may not have been following it. The portal’s reader gave up on some perfectly valid files, such as one with a /* block comment */, a trailing comma, or a value like "https://…" or "**/*.map", and carried on as if the file weren’t there, without telling anyone.

The portal now reads ee.jsonc the same way our builder does:

• Comments work, both // and /* … */, anywhere outside a string. A // inside a string, as in a URL, is just part of the string.
• Trailing commas are accepted after the last item in a list or object.
• A file that is really broken fails the deploy, with an error naming the line, instead of being skipped. When the portal is preparing to build your site, it skips a broken file with a warning.

What you need to do

If your ee.jsonc has comments or trailing commas, check it still says what you want: settings that were being ignored now take effect on your next portal deploy.