feat: support import.meta.env in worker URL template literals #21016
      
        
          +269
        
        
          −5
        
        
          
        
      
    
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Description
Implements support for template literals containing
import.meta.env.*expressions in Web Worker URL definitions.Fixes #20900
Problem
Currently, users must use string concatenation for dynamic paths with environment variables in worker URLs:
This is inconsistent with template literal usage elsewhere in Vite and less ergonomic.
Solution
Template literals with
import.meta.env.*expressions are now supported and automatically transformed:Changes
import.meta.env.*expressions allowed)playground/workerSafety
import.meta.env.*expressions in template literalsTesting
playground/workercovering:Breaking Changes
None. This is purely additive functionality.