refactor: migrate default parser to babylon

[pionxzh]

Refs:

• Bringing jscodeshift up to date facebook/jscodeshift#500

The jscodeshift a parser parameter defaults to babel5compat, which has a significantly reduced feature set from ts, babylon, etc.

This PR migrated the parser to use babylon, in the same time, drops Literal and Property.

Can we consider further migrating to @babel/core?

import { parseSync, loadOptions } from "@babel/core";

export const parser = {
  parse(code) {
    const options = loadOptions();

    return parseSync(code, options);
  },
};

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
wakaru	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 10, 2023 5:37am

[0xdevalias]

Can we consider further migrating to @babel/core?

@pionxzh Did you ever figure out/look into whether @babel/core could be used with jscodeshift?

Edit: Just checked the code and seems that's what it does under the hood anyway:

• https://github.com/facebook/jscodeshift/blob/51da1a5c4ba3707adb84416663634d4fc3141cbb/src/getParser.js#L14

  • case 'babylon':
      return require('../parser/babylon')(options);

• https://github.com/facebook/jscodeshift/blob/51da1a5c4ba3707adb84416663634d4fc3141cbb/parser/babylon.js#L11

  • const babylon = require('@babel/parser');

[pionxzh]

@0xdevalias I think it won't bring too much benefit to use babel/core for now. I saw that code snippet from somewhere I couldn't remember haha..