Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .eslintrc.json
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@
],
"parser": "@typescript-eslint/parser",
"parserOptions": {
"ecmaVersion": 2020,
"ecmaVersion": "latest",
"sourceType": "module"
},
"plugins": ["@typescript-eslint"],
Expand Down
2 changes: 1 addition & 1 deletion first-gen/.eslintrc.json
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@
],
"parser": "@typescript-eslint/parser",
"parserOptions": {
"ecmaVersion": 2020,
"ecmaVersion": "latest",
"sourceType": "module"
},
"plugins": [
Expand Down
2 changes: 1 addition & 1 deletion second-gen/.eslintrc.json
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make sure to review the linter settings we want in second-gen to ensure they are patterns we want to continue using or add new ones? This is not blocking for this PR but want to make sure we discuss as a team

cc @rubencarvalho @graynorton

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What currently is here is just a simple setup to get eslinting up and running. We can and should talk about it :)

Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@
],
"parser": "@typescript-eslint/parser",
"parserOptions": {
"ecmaVersion": 2020,
"ecmaVersion": "latest",
"sourceType": "module"
},
"plugins": [
Expand Down
7 changes: 3 additions & 4 deletions second-gen/packages/swc/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,8 @@
"cem:watch": "cem analyze --watch",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit, for consistency, could we do analyze:watch?

"clean": "rimraf dist",
"dev": "vite build --watch",
"prestorybook": "cem analyze",
"storybook": "storybook dev -p 6006",
"storybook:build": "storybook build",
"storybook": "yarn analyze && storybook dev -p 6006",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yarn cem:watch && storybook dev -p 6006?

"storybook:build": "yarn analyze && storybook build",
"test": "vitest --run",
"test:coverage": "vitest --coverage",
"test:ui": "vitest --ui",
Expand Down Expand Up @@ -92,5 +91,5 @@
"engines": {
"node": ">=20"
},
"customElements": "custom-elements.json"
"customElements": ".storybook/custom-elements.json"
}
Loading