Is there a way to make constant values show up in search results?

[nktnet1]

E.g. in constants.ts:

export const EXAMPLE = 'helloworld';

Then in example-content.mdx:

import { EXAMPLE } from './constants';

This variable will not be indexed for search: {EXAMPLE}

Is there a seamless way to make this constant value appear in searches without needing to tweak the starter search code?

Thanks!

---

Update: should also add that searching for EXAMPLE matches (false positive), and searching for "helloworld" does not match (false negative).

[fuma-nama]

No. The easiest way is to create a hidden element with the actual text value.

[nktnet1]

I see... and I take it that there's no way to make searching for the internal variable name to not show up either?

My goal is to re-use the same value across different pages, so I think adding hidden elements with the correct text will defeat that purpose.

[fuma-nama]

Using a remark plugin would be great for this purpose, it works perfectly because search indexes are built during build time on the bundler. But rendering/importing the constant requires Next.js runtime, the bundler doesn't know the actual value of constants at build time.

[nktnet1]

Thanks for the follow up @fuma-nama

Using a remark plugin would be great for this purpose

Is "purpose" in this case the ability to re-use the same value across different pages and still appear in searches? And are you saying that this is possible if I install a remark-plugin?

If so, would it be okay for you to point me in the right directions regarding the plugin?

Otherwise, if it isn't possible, no worries! Thanks!

[fuma-nama]

Really wanted to make a tutorial about writing remark plugins but I don't have time.

Basically in MAST, usages of constant value resolves to:

{test}

{
  "type": "root",
  "children": [
    {
      "type": "mdxFlowExpression",
      "value": "test",
      "data": {
        "estree": {
          "type": "Program",
          "body": [
            {
              "type": "ExpressionStatement",
              "expression": {
                "type": "Identifier",
                "name": "test"
              }
            }
          ],
          "sourceType": "module",
          "comments": []
        }
      }
    }
  ]
}

You can make a remark plugin, use unist-util-visit to walk through the tree, and replace mdxFlowExpression of a certain value with your desired node. Like a text node:

{
  "type": "text",
  "value": "some value here"
},