-
-
Notifications
You must be signed in to change notification settings - Fork 293
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
chore: update all rollup dependencies to run CI with #2114
Conversation
🦋 Changeset detectedLatest commit: b15c21b The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
74d894c
to
0a06b42
Compare
d1d61e9
to
6cdad36
Compare
3a75536
to
0dc7612
Compare
A follow up question for this (if we can get tests passing) will end up being "do we make a Rollup@3 only release?" |
@Westbrook it looks like rollup plugins have changed structure... before, a plugin had now it has |
8214fec
to
482bb44
Compare
482bb44
to
69778ea
Compare
69778ea
to
479b74b
Compare
03ba7b7
to
6974dd5
Compare
I've very naively taken all of the changes that come with this update and applied them to the tests. They feel OK-ish for the most part, but I don't 100% know what should be in this area. |
@Westbrook This is great work! Is there something I can do to help with this PR? Maybe we can do a pre-release and start testing in various environment. I'd love to take this for a spin on projects at ING to see if there's something broken that we can find. |
@koddsson A pre-release is probably a good idea! I've mainly just assumed that the process worked and accepted all of the new test rules. They're stable... which is something. If you were well versed in the sorts of transforms we're doing with CJS and ESM, extra eyes on the updated tests outputs would be a great first step. @43081j has been working a lot in this area recently, and I hope he has some time to check these changes out as well. The other area that I can think of right now would be what sort of version change this is. Technically, I don't think our APIs change, but I guess we do remove support for Rollup@2, which would be a breaking change. Would everything need to break? Just |
Yeah, I might be overly cautious here 😄 If the tests are green, that might just be fine. Then if there are issues we can make bugfix releases.
I can take a look and tell you if I spot something out of the ordinary 😄
I think a breaking change for |
Going to prerelease this now! 🤞🏼 |
|
I've updated |
@@ -33,7 +34,7 @@ describe('commonjs', () => { | |||
}); | |||
|
|||
it('can handle require default', () => { | |||
expect(requiredDefault).to.equal('foo'); | |||
expect(requiredDefault.default).to.equal('foo'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@43081j this feels like an error to have converted, in that this same wrapping of default is causing me some trouble with the canaries...thoughts?
@@ -695,6 +695,7 @@ describe('rollup-plugin-html', () => { | |||
} | |||
|
|||
const outputHtml = getAsset(output, 'index.html').source; | |||
console.log(outputHtml); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a console.log
was left in here ☝🏻
@@ -24,6 +24,7 @@ describe('commonjs', () => { | |||
}); | |||
|
|||
it('can handle compiled es modules with named exports', () => { | |||
console.log(compiledEsm); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And this console.log
What I did