Package Exports
- prettier-plugin-sql-cst
- prettier-plugin-sql-cst/dist/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (prettier-plugin-sql-cst) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Prettier plugin SQL-CST

A Prettier plugin for SQL that uses sql-parser-cst and the actual Prettier formatting algorithm.
Like Prettier for JavaScript, this plugin formats SQL expressions differently depending on their length. A short SQL query will be formatted on a single line:
SELECT a, b, c FROM tbl WHERE x > 10;A longer query, will get each clause printed on a separate line:
SELECT id, client.name, client.priority
FROM client
WHERE client.id IN (12, 18, 121);An even longer one gets the contents of each clause indented:
SELECT
client.id,
client.name AS client_name,
organization.name AS org_name,
count(orders.id) AS nr_of_orders
FROM
client
LEFT JOIN organization ON client.organization_id = organization.id
LEFT JOIN orders ON orders.client_id = client.id
WHERE
client.status = 'active'
AND client.id IN (28, 214, 457)
AND orders.status IN ('active', 'pending', 'processing')
GROUP BY client.id
ORDER BY client.name
LIMIT 100;Formatting philosophy
- Adapt formatting based on expression length.
- Stick to one style and avoid configuration options.
- Format embedded languages (like JSON data and JavaScript programs).
- When unsure, preserve existing syntax.
Currently this plugin preserves most of the syntax elements and concentrates mainly on the layout of whitespace.
See STYLE_GUIDE for overview of the SQL formatting style used.
Getting started
Install it as any other Prettier plugin:
npm install --save-dev prettier prettier-plugin-sql-cstThen use it on SQL files through Prettier command line tool or Prettier extension for your editor of choice.
Choosing an SQL dialect
By default the plugin will determine SQL dialect based on file extension:
.sqlor.sqlite- SQLite.bigquery- BigQuery
You can override this behavior with a prettier configuration:
{
"overrides": [
{
"files": ["*.sql"],
"options": { "parser": "bigquery" }
}
]
}The plugin provides the following parsers:
sqlitebigquerypostgresql(experimental! expect crashes)mysql(experimental! expect crashes)mariadb(experimental! expect crashes)
Configuration
The standard Prettier options printWidth, tabWidth, useTabs apply. There are also some SQL-specific options:
| API Option | Default | Description |
|---|---|---|
sqlKeywordCase |
upper |
Converts SQL keywords to upper or lower case, or preserve existing. |
sqlParamTypes |
[] |
Array of bound parameter types: ?, ?nr, :name, @name, $name. |
Limitations and development status
Currently this plugin supports two SQL dialects:
- SQLite - full support.
- BigQuery - full support.
It also has experimental support for the following dialects:
- PostgreSQL
- MySQL
- MariaDB
The main limitation is that the parser does not support full syntax of these dialects. One should expect the parser to crash for syntax that's more specific to these dialects. But as long as the parsing succeeds, the formatting should also succeed. Mainly one can expect the formatting of SELECT statements to work. But beyond that you should keep your expectations low. You have been warned.
The specifics of the SQL formatting style are still very much subject to change. Though the general principles should be mostly in place by now.