profile
viewpoint
Babel babel Flavortown https://babeljs.io The community maintained compiler for next generation JavaScript, today.

babel/babel 40268

🐠 Babel is a compiler for writing next generation JavaScript.

babel/babel-loader 4587

📦 Babel loader for webpack

babel/babel-preset-env 3549

PSA: this repo has been moved into babel/babel -->

babel/babel-sublime 3252

Syntax definitions for ES6 JavaScript with React JSX extensions.

babel/babel-eslint 2966

:tokyo_tower: A wrapper for Babel's parser used for ESLint (renamed to @babel/eslint-parser)

babel/babylon 1694

PSA: moved into babel/babel as @babel/parser -->

babel/babelify 1663

Browserify transform for Babel

babel/babel-upgrade 1303

⬆️ A tool for upgrading Babel versions (to v7): `npx babel-upgrade`

babel/babel-standalone 808

:video_game: Now located in the Babel repo! Standalone build of Babel for use in non-Node.js environments, including browsers.

babel/awesome-babel 798

😎A list of awesome Babel plugins, presets, etc.

startedbabel/gulp-babel

started time in 29 minutes

startedbabel/babel

started time in an hour

fork YangBo29/babel

🐠 Babel is a compiler for writing next generation JavaScript.

https://babel.dev

fork in an hour

startedbabel/babel

started time in an hour

PullRequestReviewEvent

startedbabel/babel

started time in 2 hours

startedbabel/babel

started time in 2 hours

startedbabel/babel

started time in 5 hours

startedbabel/babel

started time in 6 hours

startedbabel/babel

started time in 6 hours

fork 13168335674/babel

🐠 Babel is a compiler for writing next generation JavaScript.

https://babel.dev

fork in 6 hours

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentbabel/babel

Fix some errors that ignore startLine by adding startLine to getLineInfo

 export default class UtilParser extends Tokenizer {   checkExpressionErrors(     refExpressionErrors: ?ExpressionErrors,     andThrow: boolean,-  ) {-    if (!refExpressionErrors) return false;-    const { shorthandAssign, doubleProto, optionalParameters } =+  ): void {+    if (!andThrow || !refExpressionErrors) {+      return;

OK I went ahead and restored the old behavior I think, although I still can't seem to figure out how it behaves differently, but figured it wasn't worth blocking this PR on figuring that out. I can file a bug on exploring this further. We should try to get a test in there or figure out why it's never entered.

tolmasky

comment created time in 10 hours

PullRequestReviewEvent

Pull request review commentbabel/website

docs: target.node vs browserslist node query

 Type: `string | "current" | true`.  If you want to compile against the current node version, you can specify `"node": true` or `"node": "current"`, which would be the same as `"node": process.versions.node`. +Alternatively, you can specify node version in a browserslist query:++```jsonc+{+  "targets": "node 12" // not recommended+}+```++In this case, browserslist will interpret it as `^12.0.0`, which is resolved to

I find this confusing, because to me ^12.0.0 means "I want to support every version starting from 12.0.0. I think we should just say "browserslist will resolve it to the latest version available", without mentioning ^12.0.0.

JLHwung

comment created time in 11 hours

PullRequestReviewEvent

pull request commentbabel/babel

[test runner] Restore `TEST_GREP` support (jest's `-t` parameter)

Oh ok, right. I didn't think about it because I take a different approach: using vscode (I don't remember which editor you use), I put a breakpoint in the test file (it works well because they are not compiled, but they are executed natively), and then I run that file with this .vscode/launch.json:

{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "pwa-node",
			"request": "launch",
			"name": "Test current file",
			"program": "${workspaceFolder}/node_modules/.bin/jest",
			"args": ["${relativeFile}"]
		},
		{
			"type": "pwa-node",
			"request": "launch",
			"name": "Test current file (Babel 8)",
			"program": "${workspaceFolder}/node_modules/.bin/jest",
			"args": ["${relativeFile}"],
			"env": { "BABEL_8_BREAKING": "true" }
		}
	]
}
nicolo-ribaudo

comment created time in 11 hours

pull request commentbabel/babel

[test runner] Restore `TEST_GREP` support (jest's `-t` parameter)

Do you still wish you had --runInBand? With the lighter wrappers that we use know, I have never felt the need for it.

--runInBand is used for hooking debugger. Otherwise we have to pass --inspect-brk to each worker and figure out which worker is running the interested test. Currently I manually revise jest.config.js when I want to open a debugger.

nicolo-ribaudo

comment created time in 11 hours

pull request commentbabel/babel

[test runner] Restore `TEST_GREP` support (jest's `-t` parameter)

Q: Do you still use --runInBand? With the lighter wrappers that we use know, I have never felt the need for it.

nicolo-ribaudo

comment created time in 11 hours

PullRequestReviewEvent

pull request commentbabel/website

docs: target.node vs browserslist node query

✔️ Deploy Preview for babel ready!

🔨 Explore the source changes: 56020bf7709539a5d1cdfe5b785821deae95113e

🔍 Inspect the deploy log: https://app.netlify.com/sites/babel/deploys/61e5eb0aa54a020009565486

😎 Browse the preview: https://deploy-preview-2608--babel.netlify.app

JLHwung

comment created time in 12 hours

PullRequestReviewEvent

PR opened babel/website

docs: target.node vs browserslist node query

Clarify difference between targets.node and a browserslist node query.

Context: https://github.com/babel/babel/issues/14167#issuecomment-1014844151

+21 -89

0 comment

2 changed files

pr created time in 12 hours

pull request commentbabel/babel

[test runner] Restore `TEST_GREP` support (jest's `-t` parameter)

Nice! Thanks @nicolo-ribaudo

nicolo-ribaudo

comment created time in 12 hours

startedbabel/babel

started time in 12 hours

push eventbabel/babel

magic-akari

commit sha a6ca39cebb961255e825f3de8e8f59400df4db01

Handle logical assignment in super property transforms (#14164)

view details

push time in 12 hours

issue closedbabel/babel

[Bug]: logical assignment not handled in super property transforms

💻

  • [X] Would you like to work on a fix?

How are you using Babel?

Programmatic API (babel.transform, babel.parse)

Input code

Thanks.

Not related to this PR, but we need to add logical assignment support to super property transforms (they should have been extracted to a new helper):

class A extends B {
  async foo() {
    super.foo ??= 1;
  }
}

currently throws

Originally posted by @JLHwung in https://github.com/babel/babel/pull/14162#pullrequestreview-853689517

Configuration file name

No response

Configuration

No response

Current and expected behavior

currently throws error

Environment

Latest

Possible solution

No response

Additional context

No response

closed time in 12 hours

magic-akari

PR merged babel/babel

Handle logical assignment in super property transforms PR: Bug Fix :bug: Spec: Class Fields Spec: Logical Assignment

<!-- Before making a PR, please read our contributing guidelines https://github.com/babel/babel/blob/main/CONTRIBUTING.md

Please note that the Babel Team requires two approvals before merging most PRs.

For issue references: Add a comma-separated list of a closing word followed by the ticket number fixed by the PR. (it should be underlined in the preview if done correctly)

If you are making a change that should have a docs update: submit another PR to https://github.com/babel/website -->

Q A <!--(Can use an emoji 👍) -->
Fixed Issues? Fixes #14163
Patch: Bug Fix? 👍
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass? Yes
Documentation PR Link <!-- If only readme change, add [skip ci] to your commits -->
Any Dependency Changes?
License MIT

<!-- Describe your changes below in as much detail as possible -->

<a href="https://gitpod.io/#https://github.com/babel/babel/pull/14164"><img src="https://gitpod.io/button/open-in-gitpod.svg"/></a>

+223 -22

0 comment

2 changed files

magic-akari

pr closed time in 12 hours

PullRequestReviewEvent
more