You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, we use spaces not tabs, single quotes, and no semicolons. Additionally, if we're using a package.json file in a specific project, we'd prefer to use the prettier section in the package.json instead of the .prettierrc (and other .rc files) because we'd prefer to minimize the number of files in a project.
Additionally - we probably won't get to it for a couple more months, but for many of these services, we'd like to move away entirely from dependency on package.json and use URL-based imports (like Deno) through our own ESBuild plugin for URL imports. There will be times we still need to do continue using the package.json, specifically if we need to use node NPM libraries that also need node_compat mode in wrangler ... but then the idea will be to use a Prettier GitHub action with embedded rules instead of using NPM or Yarn
The text was updated successfully, but these errors were encountered:
We need to document this better, but the standard prettier conventions we use are:
So, we use spaces not tabs, single quotes, and no semicolons. Additionally, if we're using a
package.json
file in a specific project, we'd prefer to use the prettier section in thepackage.json
instead of the.prettierrc
(and other.rc
files) because we'd prefer to minimize the number of files in a project.Additionally - we probably won't get to it for a couple more months, but for many of these services, we'd like to move away entirely from dependency on package.json and use URL-based imports (like Deno) through our own ESBuild plugin for URL imports. There will be times we still need to do continue using the package.json, specifically if we need to use node NPM libraries that also need
node_compat
mode in wrangler ... but then the idea will be to use a Prettier GitHub action with embedded rules instead of using NPM or YarnThe text was updated successfully, but these errors were encountered: