esbuildを読む

The transform API call operates on a single string without access to a file system. This makes it ideal for use in environments without a file system (such as a browser) or as part of another tool chain.The transform API call operates on a single string without access to a file system. This makes it ideal for use in environments without a file system (such as a browser) or as part of another tool chain.

The build API call operates on one or more files in the file system. This allows the files to reference each other and be bundled together.

transformは任意の長さの文字列を変形してくれる、buildは一つまたは複数のファイルの中身を変形してくれる

ryota kise

js_parser.goにesbuildのパーサーが何をしているのかが書かれている

Parse the source into an AST, create the scope tree, and declare symbols.

Visit each node in the AST, bind identifiers to declared symbols, do constant folding, substitute compile-time variable definitions, and lower certain syntactic constructs as appropriate given the language target.
So many things have been put in so few passes because we want to minimize the number of full-tree passes to improve performance. However, we need to have at least two separate passes to handle variable hoisting. See the comment about scopesInOrder below for more information.

ryota kise

logger にtokenとかの情報が入ってる

　　　　       printer -> linker -\
input -> parser -> scanner ---> compiler -> output

NewLexer -> newParser -> Parse -> parseFile -> maybeParseFile -> scanAllDependencies -> ScanBundle -> Compile -> buildImpl -> Build
                                                                                   Printer -> link -> Compile