[Bug]: JSON translations incorrectly marked as missing

[Aridez]

Extension Version

1.0.11

PHP Binary

Local PHP

Operating System

Windows

What happened?

A warning is being thrown when using translations in JSON files, on all existing translations in a blade view, regardless of whether they exist or not.

To verify the issue, I disabled all other extensions and kept only the official Laravel extension active. After testing different versions, I found:

• The problem begins with version v1.0.8 and persists through to the latest release at the time of writing (v1.0.11)
• Version v1.0.7 does not have this issue and correctly highlights only the translations that are actually missing

Skimming through existing issues I do not see one that addresses this specifically

• [Bug]: Translation not found warning #406 references translations with a numeric keys and should be solved in Fix for translations with numeric keys #407
• [Bug]: Translation Linting is not greedy enough #370 references to translations in attributes and should be solved in Support for parser for blade component attributes #344
• Other issues seem to refer to PHP strings translations

Mimimal Code Sample

Installing a fresh Laravel 12 instance then doing php artisan lang:publish, the modified lines are the following:

resources\views\welcome.blade.php

<p class="mb-2 text-[#706f6c] dark:text-[#A1A09A]">
    {{ __('Laravel has an incredibly rich ecosystem.') }} 
    <br>
    {{ __('We suggest starting with the following.') }}
</p>

lang\en.json (created):

{
    "Laravel has an incredibly rich ecosystem.": "Laravel has an incredibly rich ecosystem."
}

Both translations are marked as missing on v1.0.11 while on v1.0.7 only the second one is correctly marked as missing.

[N1ebieski]

For me, it works:

What do you have in the app.locale config?

[Aridez]

Hey thanks for the reply!

My app.locale should be the default, this is the value it has:

    'locale' => env('APP_LOCALE', 'en'),

After fiddling a bit more with the issue, it has me stumped. It seems like I cannot reliably reproduce it with the minimal code sample I put before. It sometimes works and sometimes doesn't, but I think it has to do with this attached JSON:

en.json

If I place the translation at the top of it, it gets detected properly, but placing it at the bottom (as it is in this JSON), marks it as undefined.

I think there's something in that JSON the extension doesn't like, but I cannot pinpoint what exactly is. I even ran it through a checker just for sanity and didn't find any issues with it.

Can you reproduce the issue using that file?

In case it is helpful, I also found that other people seem to face a similar issue, in the latest comments on #118 and #73 that seem to come up first through google results. Also seem to be related to v1.0.7.

[N1ebieski]

@Aridez with your en.json, it still works for me.

[Aridez]

Thanks for checking it.

I'm all out of ideas now, I tried completely deleting vscode and reinstalling it, but the issue with that JSON persists on my end.

I'll fall back to v1.0.7 for now and hopefully things get back working in the future again.

Not sure what could be causing it, but if you got anything else I could try to troubleshoot this let me know, I'd really appreciate it.

[Aridez]

Hey @N1ebieski, I was able to resolve the issue.

It turns out the problem was caused by line endings in the JSON files. It seems the jump from v1.0.7 to v1.0.8 may have changed how these files are parsed.

Specifically, the failing JSON was using LF instead of CRLF while working on Windows. Switching to CRLF fixed the issue.

This might be worth looking into to prevent others from running into the same issue. Interestingly, version v1.0.7 seemed to handle both line ending types without any problems.

However, I did notice some odd behavior. When there's a line ending mismatch like this one, the extension only reads the first six lines of translations correctly, and then fails on every translation from the 7th line onward.

If you don’t think this is significant enough to address in an update, feel free to close the issue.