Size Change: +13.5 kB (1%)

Total Size: 883 kB

_{compressed-size-action}

Noting that, It’s yet another thing to take into account when creating a package. Should we introduce package scaffolding tool? 😅

Yeah, part of this was to just to demonstrate (even for myself) the amount of effort which would be involved as of the changes resulting from #18942. I think a scaffolding tool could be useful. I was also considering whether it could be the sort of thing where a bot would comment on a pull request where a new package is being added, which could do a few things:

• Include a checklist of tasks to complete (and automatically update them as checked once completed)
• Reference relevant documentation
• Ping the core development team (since it affects a public interface)

In theory, a bot could even do the commits itself.

Just to reiterate: This is currently blocked by #18942. My plan would be to wait for #18942 to be merged, then change the base of this pull request to master and merge.

It sounds like a plan 👍

I want to use this PR to add types for create block a scripts packages at some point in the near future 😃

@sirreal I see you did a force push recently that introduced quite a few unexpected changes and merge conflicts. Do you know what might have happened?

I force pushed to the base branch (#18942) after rebasing against master to fix conflicts.

Ah, I guess I didn't anticipate those sorts of changes in your branch would surface up so prominently in this pull request 🤔

No matter, I should be able to get it resolved without much trouble. Likely just needs a rebase against your newly-rebased branch.

I've pushed more changes to the base branch and appear to have introduced more conflicts. Sorry!

It's a sign that it's time to land #18942 😁

It's a sign that it's time to land #18942 😁

Yes 😄 , but also....

I've pushed more changes to the base branch and appear to have introduced more conflicts. Sorry!

It looks bad, but I doubt there are actually any conflicts to resolve.

Noting that I'm intentionally choosing not to include a CHANGELOG entry for this change because there isn't yet a published version of this package (i.e. it technically still qualified under the current "initial release" note).

I neglected to include necessary changes here. Don't use this pull request as reference 😬

See #21381