Skip to content
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 esbuild #343

Merged
merged 1 commit into from
Jan 31, 2022
Merged

chore: update esbuild #343

merged 1 commit into from
Jan 31, 2022

Conversation

threepointone
Copy link
Contributor

Update esbuild to 0.14.14. Also had to change import esbuild from "esbuild"; to import * as esbuild from "esbuild"; in dev.tsx.

@changeset-bot
Copy link

changeset-bot bot commented Jan 30, 2022

🦋 Changeset detected

Latest commit: 028fe95

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
wrangler Patch

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

Update esbuild to 0.14.14. Also had to change `import esbuild from "esbuild";` to `import * as esbuild from "esbuild";` in `dev.tsx`.
Copy link
Contributor

@JacobMGEvans JacobMGEvans left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like an added benefit of less code 😃

@GregBrimble GregBrimble mentioned this pull request Jan 31, 2022
@threepointone threepointone merged commit cfd8ba5 into main Jan 31, 2022
@threepointone threepointone deleted the update-esbuild branch January 31, 2022 09:03
@github-actions github-actions bot mentioned this pull request Jan 31, 2022
Copy link
Contributor

@petebacondarwin petebacondarwin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we should standardise these kind of imports.
Before this PR we had

import esbuild from "esbuild"; // using a default export, which I guess has now disappeared?
import * as esbuild from "esbuild"; // importing the module as a namespace
import type {BuildResult} from "esbuild"; // just bringing in a type for type checking
import {build} from "esbuild"; // just bringing in the build function directly.

In general, I prefer the last two syntaxes unless the namespace contains dozens of exports that we are using in the file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

3 participants