Nuxt•2w ago

Vitual file not defined

I'm trying to create a virtual file within the

nitro:config

nitro:config

nitro:config

nitro:config hook of my module using

addTemplate({
  filename: 'rpcMethodsTypes.mjs',
  getContents: () => `
  export default ${JSON.stringify(mappedRpcMethods, null, 2)} `,
})

addTemplate({
  filename: 'rpcMethodsTypes.mjs',
  getContents: () => `
  export default ${JSON.stringify(mappedRpcMethods, null, 2)} `,
})

addTemplate({
  filename: 'rpcMethodsTypes.mjs',
  getContents: () => `
  export default ${JSON.stringify(mappedRpcMethods, null, 2)} `,
})

addTemplate({
  filename: 'rpcMethodsTypes.mjs',
  getContents: () => `
  export default ${JSON.stringify(mappedRpcMethods, null, 2)} `,
})

However, when I try to import this file in a composable I always the error message

Package import specifier is not defined

Package import specifier is not defined

Package import specifier is not defined

Package import specifier is not defined when running the an app using this module.

I also tried

addServerTemplate

addServerTemplate

addServerTemplate

addServerTemplate but I still get the same error. Am I missing something?

kapa.ai•12/18/25, 8:02 AM

Hi @lutejka. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

kapa.ai•12/18/25, 8:02 AM

----------------------
addTemplateaddTemplate /

addServerTemplate

addServerTemplate

only creates the (virtual) file and type mappings – it does not automatically give you a usable import specifier. You need to:

1. Give the template a virtual path (with a leading ##) and
2. Import that same virtual path from your composable.

From the available docs we know:

-

addServerTemplate

addServerTemplate

is specifically meant for Nitro virtual files.

addServerTemplate

addServerTemplate

- addTypeTemplateaddTypeTemplate / addTemplateaddTemplate can also augment Nuxt/Nitro types, but only when configured with proper paths and contexts.addTypeTemplateaddTypeTemplate
- addTemplateaddTemplate now initializes tsconfigtsconfig paths if they are undefined, to support these virtual paths correctly.addTemplate pathsaddTemplate paths

What’s not shown in the sources is an explicit example of how to declare the srcsrc/aliasalias for a runtime-usable virtual module, so the knowledge sources don’t provide the exact import string you should use. I'm therefore not able to state confidently which specifier (#rpc-methods#rpc-methods, #build/...#build/..., etc.) Nuxt would generate from your specific addTemplateaddTemplate call.

Given the information we do have, the likely issues are:

- The template is created without a corresponding alias / path mapping in Nuxt/Nitro config.
- The import in your composable doesn’t match the generated specifier (or it’s using a Vue app alias on the server, which Nitro explicitly disallows in some cases).nitro alias protectionsnitro alias protections

Since the docs in the provided sources don’t show the concrete pattern for runtime imports of addTemplateaddTemplate/

addServerTemplate

addServerTemplate

outputs, I can’t give you a guaranteed working code snippet.

To move forward within what the sources cover, you could:

kapa.ai•12/18/25, 8:02 AM

- Use

addServerTemplate

addServerTemplate

for your Nitro-only virtual file, ensuring it’s clearly in the server context.

addServerTemplate

addServerTemplate

- If you’re only augmenting types, prefer addTypeTemplateaddTypeTemplate so Nuxt/Nitro type contexts are handled for you.addTypeTemplateaddTypeTemplate

But for the exact “Package import specifier is not defined” error and how to import this specific rpcMethodsTypes.mjsrpcMethodsTypes.mjs in a composable, the knowledge sources don’t provide enough detail to say precisely what is missing (alias key, filename pattern, or import path) or to show the correct final code.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•12/18/25, 8:02 AM

@1437507434519330957 Kapa.ai is still learning and improving, please let me know how I did by reacting below.

lutejkaOP•12/18/25, 8:09 AM

I did use #build/rpcMethodsTypes.mjs#build/rpcMethodsTypes.mjs to import the file. When I check the virtual file system using the /_vfs path of my app. I also see it generated. But I still cannt import it @kapa.ai

lutejkaOP•12/18/25, 12:50 PM

@kapa.ai

kapa.ai•12/18/25, 12:50 PM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•12/18/25, 12:50 PM

Sorry @lutejka, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

lutejkaOP•12/18/25, 4:37 PM

@kapa.ai

kapa.ai•12/18/25, 4:37 PM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•12/18/25, 4:37 PM

Sorry @lutejka, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

lutejkaOP•12/18/25, 4:38 PM

@kapa.ai any idea ?

kapa.ai•12/18/25, 4:38 PM

Let me check the knowledge base for you again. One moment! :books:

kapa.ai•12/18/25, 4:38 PM

----------------------
The knowledge sources don’t show a full, working example of importing a runtime virtual file created with addTemplateaddTemplate /

addServerTemplate

addServerTemplate

, so I can’t say with certainty which exact import specifier you should use in your composable.

What is clear from the sources:

-

addServerTemplate

addServerTemplate

is specifically for Nitro virtual files (server context). [addServerTemplate]
- addTemplateaddTemplate now initializes tsconfigtsconfig paths when needed, so virtual paths like #something#something can be wired up, but the docs here don’t show the exact mapping from filenamefilename to import specifier. [addTemplate paths]
- There’s also a distinction between Nuxt and Nitro contexts when generating types / templates (addTypeTemplateaddTypeTemplate can target both), which suggests that where you call addTemplateaddTemplate (Nuxt vs Nitro context) affects how it’s resolved. [addTypeTemplate]

Because of that missing piece, I can’t reliably tell you:

- What import path (e.g. #rpcMethodsTypes#rpcMethodsTypes, #build/rpcMethodsTypes#build/rpcMethodsTypes, etc.) Nuxt/Nitro is actually generating for your rpcMethodsTypes.mjsrpcMethodsTypes.mjs, or
- Whether additional alias configuration is required in your module to make that file importable from a composable.

So all I can say with confidence, based on the sources, is:

- Using

addServerTemplate

addServerTemplate

is the right direction for a Nitro virtual file. [addServerTemplate]
- The “Package import specifier is not defined” error likely means the import path you’re using in the composable does not match any generated virtual module / alias, but the provided docs don’t specify how to derive the correct one from your addTemplateaddTemplate call.

If you can share:

kapa.ai•12/18/25, 4:38 PM

- The exact import statement you’re using in the composable, and
- How you’re trying to reference this template (any ## alias, etc.),

then with more context (or additional docs) it might be possible to narrow down the issue, but with the current knowledge sources I can’t give a precise fix.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------

kapa.ai•12/18/25, 4:38 PM

@1437507434519330957 Kapa.ai is still learning and improving, please let me know how I did by reacting below.

Vitual file not defined

Similar Threads

Similar Threads

Similar Threads