Rest 1/2 of Disable dynamic import wrapper __vite__injectQuery #16678

Activity

1. b5414

   added

   enhancement: pending triage

   on May 14, 2024
2. sapphi-red commented on May 17, 2024

   

   sapphi-red

   on May 17, 2024

   Member

   More actions

   Unfortunately we cannot simply skip injecting __vite__injectQuery as it'll break some apps (#14851 (comment)). I guess #9981 could solve this in an ideal way.
3. b5414 commented on May 17, 2024

   

   b5414

   on May 17, 2024

   Last edited by b5414

   Author

   More actions

   @sapphi-red why not?

   now VITE is bipolar: on build you got one result, and on running dev - different

   You can jump into my sample repo and check why is it important, at least for my existing (and prod) case

   ---

   Idk what is your #9981 case, but if it should work with my case - please, just show me, and reply with comment, like why is it should be "this crunch" and not the All-In-One-Box tool (as vite is, by mho)
4. b5414 commented on Jun 3, 2024

   

   b5414

   on Jun 3, 2024

   Author

   More actions

   The problem is that I don't manage the file connection/importanation and configureServer with server.middlewares.use doesn't work well, I have tried specifying "?import" in paths but all in vain;

   The whole script runs in the "service-worker" (background.js) file where I can't use dynamic loading of files and then the TEXT (directory path for example) goes to the chrome tab where I can't DIRECTLY take the file from the extension's local path as required by the CHROME API

   ---

   because I believe this text above is hard to understand, once again:

   • func_super_for_inject function which going to be JSON.stringify then JSON.parse by CHROME during the execFunc

   • whole body of func_super_for_inject is ISOLATED, and I only can give the SIMPLE params by arguments, like basic_file_dir

   I have tried:

   • const basic_file_dir = '/rendered/assets/basic.js';
   • const basic_file_dir = 'http://localhost:3000/rendered/assets/basic.js?import'; // direct dev path
   • const basic_file_dir = chrome.runtime.getURL('/rendered/assets/basic.js' + '?import');
   • const basic_file_dir = chrome.runtime.getURL('/rendered/assets/basic.js') + '?import';

   and I have seen the trying path at console log

   and I believe configureServer(server) + server.middlewares.use works only on NOT dynamic import (it means: it's not my case)
5. sapphi-red

   added the

   Feature

   issue type on Mar 3, 2025
6. sapphi-red

   added

   pending triage

   and removed

   enhancement: pending triage

   on Mar 3, 2025
7. FranklinWhale commented on Aug 26, 2025

   

   FranklinWhale

   on Aug 26, 2025

   More actions

   __vite__injectQuery is breaking import() with import attributes.

   await import(/* @vite-ignore */`/api/${path}`, { with: { type: "json" } });

   becomes

   await import(
     /* @vite-ignore */
     __vite__injectQuery(`/api/${path}`,
     { with: { type: "json" } }, 'import')
   )

   👍React with 👍1Reacted by Nicolò Ribaudo
8. ins429 commented on Aug 28, 2025

   

   ins429

   on Aug 28, 2025

   More actions

   Any progress with this?
9. shacha086 commented on Jan 5, 2026

   

   shacha086

   on Jan 5, 2026

   Last edited by shacha086

   More actions

   If I do something like

   if (pm.type === "module") {
       import(storage_url).then((module) => {
           that.kag.ftag.nextOrder();
       });
   }
   

   the import analyser will prepend import {injectQuery as __vite__injectQuery} from "/@vite/client"; into script and it will crash on non-esm runtime. Adding file to optimizeDeps.exclude doesn't helps either. It’s better to have a master switch that completely disables this injection.
10. nicolo-ribaudo commented on Apr 20, 2026

    

    nicolo-ribaudo

    on Apr 20, 2026

    Contributor

    More actions

    I'm struggling with this same problem. I have a non-analyzable import that loads an external resource:

    const cssUrl = "https://example.com/foo.css"
    
    function load() {
      import(/* @vite-ignore */ cssUrl, { with: { type: "css" } })
    }

    And Vite is producing this output, removing the import attributes:

    function load() {
      import(
    	/* @vite-ignore */
    	__vite__injectQuery(cssUrl, { with: { type: "css" } }, 'import')
      );
    }

    I am happy to contribute a fix, but I need pointers in what the expected behavior would be.
11. nicolo-ribaudo commented on Apr 20, 2026

    

    nicolo-ribaudo

    on Apr 20, 2026

    Contributor

    More actions

    This might be an es-module-lexer bug: guybedford/es-module-lexer#196