node-sdk
                                
                                
                                
                                    node-sdk copied to clipboard
                            
                            
                            
                        upgrade to yarn 4
Note: breaking change (requires node>=18)
TODO
- [ ] replace np with something that works with yarn 4 (and update readme) #169
 
I've tried to tinker with upgrading np to support yarn berry and it seems to be working, but I haven't done tests yet: https://github.com/mifi/np/pull/1
upstream np accepts yarn 4 now as indicated in https://github.com/mifi/np/pull/1, so we could likely upgrade np along with yarn and settle here
yes but I think it would be a breaking change?
Only for contributors, not for consuming devs that added it as a dependency correct? Can’t they just npm/pnpm/yarn1 install this when it’s part of a project?
I’m running into the same problem in #176. Vitest also requires Node.js >=18. Although I personally prefer to test against all supported Node.js versions, I suggest we drop tests for Node.js 14 and 16 so we can upgrade Yarn and Vitest. The upcoming TypeScript migration will define a target matching Node.js 14, so the odds of breaking Node.js 14 support are slim.
yea im fine with not testing against old versions for now