- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 611
fix(terser): upgrade serialize-javascript #1932
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
      
        
              This comment was marked as off-topic.
        
        
      
    
  This comment was marked as off-topic.
      
        
              This comment was marked as off-topic.
        
        
      
    
  This comment was marked as off-topic.
      
        
              This comment was marked as off-topic.
        
        
      
    
  This comment was marked as off-topic.
| @krausvo1 if agentHits is your bot please remove it. | 
| 
 It is not, never seen this thing before. | 
      
        
              This comment was marked as off-topic.
        
        
      
    
  This comment was marked as off-topic.
| @agentHits please cease commenting on this PR. | 
| @krausvo1 this update is causing a panic in the tests. check out the failing workflow:  | 
| @CharlieHelps please analyze the failing Node 18 test and the dependency that was updated in this PR, and share any findings as to why that v8 error is being thrown between the two versions of the dependency that is being updated. | 
| This issue feels a little out of my league tbh and I have no idea why my changes would cause this issue. This is what I was able to find out so far: 
 Do you think it makes sense to disable worker threads for terser's tests? | 
| Totally understand. I'm going to see if I can use an agent to move the tests to vitest and off of Ava (it's gotten worse over the years, while vitest has gotten better). Will keep this one open. | 
Rollup Plugin Name:
terserThis PR contains:
Are tests included?
Breaking Changes?
If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers:
Description
This PR bumps serialize-javascript from 6.0.1 to 6.0.2 which includes XSS vulnerability fix. There are no breaking changes in 6.0.2.