Closed TimDaub closed 3 years ago
Latest commit: f155eee1982169735ce5ededdd370e0f014f01f8
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@developit I addressed your comments. I'm not sure I'm capable of rebasing though. Last time I tried sketchy things happened in package-lock.json that I wasn't able to address. What now?
Last time I tried sketchy things happened in package-lock.json that I wasn't able to address.
You generally have to accept the remote one and then after create a new commit / amend a commit with a file you generated after by running npm install
I'll try to get this rebased this week (I'm also terrible at it!).
This will need to go into a new breaking release (minor since microbundle is still pre-1.0), but I think that should be fine.
Just wanted to mention I haven't forgotten about this PR, I just have been side-tracked rewriting Microbundle's filename inference.
This was landed in #867! 🎉
Few comments
🤞🏼 that somehow this gets merged!