Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rajasegar/ast-tooling
Monorepo for all AST tooling
https://github.com/rajasegar/ast-tooling
Last synced: 4 days ago
JSON representation
Monorepo for all AST tooling
- Host: GitHub
- URL: https://github.com/rajasegar/ast-tooling
- Owner: rajasegar
- Created: 2022-05-16T10:28:05.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2023-11-18T07:25:55.000Z (12 months ago)
- Last Synced: 2024-05-16T17:20:58.085Z (6 months ago)
- Language: JavaScript
- Homepage: https://ast-tooling.vercel.app/
- Size: 1.25 MB
- Stars: 10
- Watchers: 3
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
Awesome Lists containing this project
README
# AST Tooling
All the AST tooling library in one place using Turborepo and pnpm
This is an official starter turborepo.
## What's inside?
This turborepo uses [pnpm](https://pnpm.io) as a packages manager. It includes the following packages/apps:
### Apps and Packages
- `web`: a web app called `AST-Tooling`
- `ast-node-builder`: an npm library used by `AST-Tooling`
- `ast-node-finder`: an npm library used by `AST-Tooling`
- `config`: `eslint` configurations (includes `eslint-config-next` and `eslint-config-prettier`)
- `tsconfig`: `tsconfig.json`s used throughout the monorepo
### Utilities
This turborepo has some additional tools already setup for you:
- [TypeScript](https://www.typescriptlang.org/) for static type checking
- [ESLint](https://eslint.org/) for code linting
- [Prettier](https://prettier.io) for code formatting
## Setup
This repository is used in the `npx create-turbo@latest` command, and selected when choosing which package manager you wish to use with your monorepo (PNPM).
### Build
To build all apps and packages, run the following command:
```
cd ast-tooling
pnpm run build
```
### Develop
To develop all apps and packages, run the following command:
```
cd ast-tooling
pnpm run dev
```
### Remote Caching
Turborepo can use a technique known as [Remote Caching (Beta)](https://turborepo.org/docs/features/remote-caching) to share cache artifacts across machines, enabling you to share build caches with your team and CI/CD pipelines.
By default, Turborepo will cache locally. To enable Remote Caching (Beta) you will need an account with Vercel. If you don't have an account you can [create one](https://vercel.com/signup), then enter the following commands:
```
cd ast-tooling
pnpx turbo login
```
This will authenticate the Turborepo CLI with your [Vercel account](https://vercel.com/docs/concepts/personal-accounts/overview).
Next, you can link your Turborepo to your Remote Cache by running the following command from the root of your turborepo:
```
pnpx turbo link
```
## Useful Links
Learn more about the power of Turborepo:
- [Pipelines](https://turborepo.org/docs/features/pipelines)
- [Caching](https://turborepo.org/docs/features/caching)
- [Remote Caching (Beta)](https://turborepo.org/docs/features/remote-caching)
- [Scoped Tasks](https://turborepo.org/docs/features/scopes)
- [Configuration Options](https://turborepo.org/docs/reference/configuration)
- [CLI Usage](https://turborepo.org/docs/reference/command-line-reference)