Merged
Conversation
d8489e7 to
11eec4d
Compare
11eec4d to
c9c44b8
Compare
threepointone
approved these changes
Jan 26, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
wrangler@0.0.13
Patch Changes
#293
71b0fabThanks @petebacondarwin! - fix: warn if thesite.entry-pointconfiguration is found during publishingAlso updates the message and adds a test for the error when there is no entry-point specified.
Fixes Deprecate support for
sites['entry-point']configuration: you don't need that if you're explicitly passing the script. #282#304
7477b52Thanks @threepointone! - feat: enhancewrangler initThis PR adds some enhancements/fixes to the
wrangler initcommand.wrangler.tomlif it already existswranglerwhen creatingpackage.jsonwranglerintopackage.jsoneven ifpackage.jsonalready exists@cloudflare/workers-typeseven iftsconfig.jsonalready existsThis does have the side effect of making out tests slower. I added
--prefer-offlineto thenpm installcalls to make this a shade quicker, but I can't figure out a good way of mocking these. I'll think about it some more later. We should work on making the installs themselves quicker (re: generate a compiled version of miniflare #66)This PR also fixes a bug with our tests -
runWranglerwould catch thrown errors, and if we didn't manually verify the error, tests would pass. Instead, it now throws correctly, and I modified all the tests to assert on thrown errors. It seems like a lot, but it was just mechanical rewriting.#294
7746fbaThanks @threepointone! - feature: add more types that get logged viaconsolemethodsThis PR adds more special logic for some data types that get logged via
consolemethods. Types likePromise,Date,WeakMaps, and some more, now get logged correctly (or at least, better than they used to).This PR also fixes a sinister bug - the
typeof theConsoleAPICalledevents don't match 1:1 with actual console methods (eg:console.warnmessage type iswarning). This PR adds a mapping between those types and method names. Some methods don't seem to have a message type, I'm not sure why, but we'll get to them later.#310
52c99eeThanks @threepointone! - feat: error if a site definition doesn't have abucketfieldThis adds an assertion error for making sure a
[site]definition always has abucketfield.As a cleanup, I made some small fixes to theConfigtype definition, and modified the tests inpublish.test.tsto use the config format when creating awrangler.tomlfile.