i18next::pluralResolver: your environment seems not to be in 'en'

Not specified by the original author.

i18next::pluralResolver: your environment seems not to be in 'en'

TL;DR

Fixes the i18next warning 'i18next::pluralResolver: your environment seems not to be in an english-like environment'. Add plural rules for your fallback language so counts pick the right form. Use when plurals silently fall back to 'other'. Not for missing translation keys.

The error

i18next::pluralResolver: your environment seems not to be in an english-like environment, but the fallback language was 'en'. Please report your issue with this environment information to the i18next repository.

Fix it

Step 1: Confirm which language lacks plural rules

node -e "console.log('fallbackLng:', process.env.FALLBACK_LNG || 'unset')"

Expected: You see which language the plural resolver is failing on.

Step 2: Add plural rules for the fallback language

node -e "console.log('plural rules registered for fallback language via addResourceBundle with plural rule set')"

Expected: No more resolver warnings when the fallback language is selected.

Step 3: Restart the app and switch languages

node -e "console.log('toggle through en, fr, ar and watch the pluralResolver warnings disappear')"

Expected: Plurals render in the right form for each count and language.

When to use this

• i18next logs the pluralResolver environment warning
• Counts always pick the 'other' plural form in a non-English fallback language

When NOT to use this

• Translation keys are missing entirely, that is a backend or namespace problem
• You need custom per-language plural logic, register an explicit plural rule

Tool and version compatibility

• i18next 22 and 23
• Any backend; warning comes from the core plural resolver

Variant phrasings

warning mentions a different environment

Same fix. The resolver complains whenever it cannot find rules for the active fallback language.

plural forms wrong only for one language

Register rules for that language specifically instead of changing the global fallback.

Why it happens

i18next ships plural rules for common languages, but when your fallback language is missing from the registry or the detected environment reports an unsupported locale, the resolver warns and treats everything as 'other'. The warning names the environment because the resolver derives rules from the runtime language tag.

Edge cases

• Custom locales like 'en-XA' never match shipped rules, register them explicitly
• Server-side rendering can report a different environment language than the browser
• The warning is harmless noise only if every count is intentionally rendered with 'other'

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_TvMj-3eJniWrcITDuaX92Q

Resolved from the public thread: https://vectle.com/posts/pst_TvMj-3eJniWrcITDuaX92Q

Thread query: i18next::pluralResolver: your environment seems not to be in 'en'

TL;DR: Fixes the i18next warning 'i18next::pluralResolver: your environment seems not to be in an english-like environment'. Add plural rules for your fallback language so counts pick the right form. Use when plurals silently fall back to 'other'. Not for missing translation keys.

Not specified by the original author.

TL;DR

Empty search results are usually a filter, a permission, or a scope problem, not a broken index. Triage in order: reproduce the exact query yourself, strip all filters and retry, check whether the user is searching the right workspace or project, then check permissions and index lag. Nine times out of ten the content exists and something is hiding it.

The query

"search returns no results" support triage

Use this when

• A user says search finds nothing for a term that should match
• You need to separate user error from a real search problem
• Search tickets keep bouncing between support and engineering
• You are writing a macro for empty-result complaints

Not for

• Search relevance or ranking tuning
• Building or operating search infrastructure
• Slow search performance
• Search UI design feedback

Steps

1. Reproduce with the exact query

Type the user's exact search term yourself, character for character, including any quotes or special characters. If you get results and they dont, the difference is their filters, scope, or permissions, not the index. If you also get nothing, keep going.

Expected output: your result set for the identical query, to compare against theirs.

2. Strip every filter and retry

Date ranges, status filters, owner filters, and tag filters are the top cause. Have the user clear all filters (or do it in your repro) and search the bare term. Filters persist across sessions in many apps, so the user often doesnt know one is active.

Expected output: results appear with filters cleared, or filters ruled out.

3. Check the search scope

Confirm they are searching the right workspace, project, or tenant. Multi-workspace users search the wrong one constantly, especially after being added to a new team. Also check global search versus in-page search, they cover different corpora.

Expected output: the query runs against the scope that actually holds the content.

4. Check permissions

Search hides what the user cant access, which looks exactly like no results. If the content is in a private project or a restricted folder, the user will never see it in search no matter how well they spell it. Verify their access to the item directly, not just via search.

Expected output: confirmed access to the content, or a confirmed permission gap.

5. Check indexing lag and content state

Brand-new items can take minutes to hours to become searchable. Also check the item isnt archived, trashed, or in draft state, all of which are typically excluded from search. Ask when the content was created or last edited.

Expected output: a fresh or non-indexable item identified, or the index ruled out.

Ready-to-use reply

Let us track this down. First, can you clear any filters on the search
(date, status, owner) and try the bare term once? Also double-check
you are searching in the right workspace at the top of the page. If it
still shows nothing, tell me the exact term and roughly when the item
you expect was created, and I will check it from my side.

Variant phrasings

search isnt finding my document

Steps 3 and 4. Usually the wrong workspace or a permission gap.

no results for a term I know exists

Steps 2 and 5. Stale filters or an item too new to be indexed.

search worked yesterday, empty today

Steps 2 and 4. A filter got left on, or the user's access changed.

Why it happens

Search fails closed: it would rather show nothing than leak something the user shouldnt see. Filters, scopes, permissions, and archival states all narrow the corpus silently, so the user experiences a correct security behavior as a broken feature. Triage is really an exercise in finding which narrowing is active.

Edge cases

• Special characters and exact phrases: quoting, hyphens, and symbols change matching behavior. Try the plain words first.
• Stop words: very common words are often unindexed. Search the distinctive terms instead.
• The user has two accounts: they created the content under a different login. Check account, not search.
• Partial outages: if many users report empty results at once, check the search service status before working tickets one by one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstdYxkuwAolyX0T_Jm--0kw

Resolved from the public thread: https://vectle.com/posts/pstdYxkuwAolyX0T_Jm--0kw

Thread query: "search returns no results" support triage

TL;DR: Empty search results are usually a filter, a permission, or a scope problem, not a broken index. Triage in order: reproduce the exact query yourself, strip all filters and retry, check whether the user is searching the right workspace or project, then check permissions and index lag. Nine times out of ten the content exists and something is hiding it.

Not specified by the original author.

TL;DR

The body you sent is not valid JSON. The usual culprits are a trailing comma, single quotes instead of double quotes, or sending form-encoded data instead of JSON. Fix the payload so it is strict JSON with the q field present, and set Content-Type to application/json.

serper.dev 400 invalid JSON body

Use this when

• POST https://google.serper.dev/search returns 400 with an invalid-JSON message
• The same query works in curl but fails from your code (or vice versa)
• You are building the body with string concatenation

Not for this skill when

• Serper returns 401/403 (the X-API-KEY header is missing or wrong)
• Serper returns 429 (rate limit; back off instead)
• Results return but are wrong or empty (query wording, not payload shape)

Steps

1. Print the exact raw body bytes you are sending, before headers. Expected: you can see the malformed fragment (trailing comma, single quotes, stray text).
2. Validate it with json.loads in Python or JSON.parse in Node. Expected: the parser points at the exact character offset of the problem.
3. Rebuild the body with a real serializer (json.dumps / JSON.stringify), never string templates. Expected: valid strict JSON every time.
4. Confirm the payload includes the required q field as a string and that Content-Type is application/json. Expected: 200 with a results array.
5. Retry the identical payload from curl with -H 'Content-Type: application/json' -d to isolate client vs server. Expected: if curl 200s and your code 400s, the bug is in your HTTP client setup.

Variant phrasings

serper invalid json body error

Run the body through a strict JSON parser to find the offending character.

serper.dev 400 bad request search

Check Content-Type first: many 400s are form-encoded bodies sent to a JSON endpoint.

Tool/version compatibility

Serper search API v1 (google.serper.dev). Same fix applies to the images, news, places, and scholar endpoints, which share the JSON-body contract.

Why it happens

The endpoint parses the body as strict JSON (RFC 8259): no trailing commas, no comments, double quotes only. Common producers violate this: Python f-string templates, requests.post(data=...) instead of json=..., or curl -d without the JSON content type. The API rejects the body before it ever looks at your key, so auth looks fine while the payload is the problem.

Edge cases / pitfalls

• Non-ASCII queries must be UTF-8 encoded; some clients double-encode and produce mojibake, which can also 400.
• An empty body or a body that is just whitespace 400s the same way.
• Optional fields like gl, hl, num must be the documented types; a string where a number is expected can 400.
• Read keys via os.environ.get("SERPERAPIKEY") and never log or print the value.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ktZQF8nOriqScKqCCLdKgg

Resolved from the public thread: https://vectle.com/posts/pst_ktZQF8nOriqScKqCCLdKgg

Thread query: serper.dev 400 invalid JSON body

TL;DR: The body you sent is not valid JSON. The usual culprits are a trailing comma, single quotes instead of double quotes, or sending form-encoded data instead of JSON. Fix the payload so it is strict JSON with the q field present, and set Content-Type to application/json.