Astro v4 upgrade (#783)

* upgrade to astro v2

* upgrade to astro 3

* upgrade packages for astro v4

* fix eslint

* fix the pre-commit hook

* run lint formatters

* temporarily disable tsconfig rules

* remove old package placeholders for amplify deployment

* add first pass at unified content collection config

* add all content via content collections

* remove deprecated amplify config

* run formatter

* migrate collection data to new format

* run migration against latest schema decisions

* create content collection config with all collections

* remove old data files

* remove unused reference to libraryTags

* update migration script for images

* update todo list

* update content and pull in assets

* update tsconfig and add path alliases

* update data fetchers and fix types

* add initial cli

* ensure flatMap on getStaticPaths

* fix example-content to match schema

* refactor tags and types into discrete files

* fix type issues

* remove redundant layout

* enable semi-colon in prettier and format

* add entry auto generator script

* fix svg assets

* fix how images are consumed

* fix angular, react, and vue assets

* fix remaining content

* remove plop usage

* fix site build via astro config

See https://docs.astro.build/en/guides/troubleshooting/#adding-dependencies-to-astro-in-a-monorepo

* update README

* update yarn for version compat

* upgrade storybook

* update stories

* remove todo list

* add realworld svelte book to keep in sync with main

* fix type issues

* fix google analytics script import

* remove fragment breaking google analytics from rendering

.eslintrc.js

@@ -1,35 +1,44 @@
 module.exports = {
-	parser: "@typescript-eslint/parser", // Specifies the ESLint parser
-	parserOptions: {
-		ecmaVersion: 2020, // Allows for the parsing of modern ECMAScript features
-		sourceType: "module", // Allows for the use of imports
-		ecmaFeatures: {
-			jsx: true, // Allows for the parsing of JSX
-		},
+	env: {
+		browser: true,
+		es2021: true,
+		node: true,
 	},
 	extends: [
-		"plugin:@typescript-eslint/recommended",
-		"plugin:react/recommended",
-		"plugin:react-hooks/recommended",
-		"prettier",
+		'plugin:@typescript-eslint/recommended',
+		'plugin:react/recommended',
+		'plugin:react-hooks/recommended',
+		'prettier',
+		'plugin:astro/recommended',
+	],
+	overrides: [
+		{
+			env: {
+				node: true,
+			},
+			files: ['.eslintrc.{js,cjs}'],
+			parserOptions: {
+				sourceType: 'script',
+			},
+		},
 	],
+	parserOptions: {
+		ecmaVersion: 'latest',
+		sourceType: 'module',
+	},
+	plugins: ['react'],
 	rules: {
 		// Story files should not be imported
-		"no-restricted-imports": ["error", { patterns: ["*.stories"] }],
+		'no-restricted-imports': ['error', { patterns: ['*.stories'] }],
 		// This is not necessary and conflicts with typescript's no unused vars
-		"react/react-in-jsx-scope": "off",
+		'react/react-in-jsx-scope': 'off',
 		// This causes false positives when props are correctly inferred
-		"react/prop-types": "off",
+		'react/prop-types': 'off',
 		// Empty interfaces are useful as aliases to be filled in later
-		"@typescript-eslint/no-empty-interface": "off",
-		"@typescript-eslint/no-unused-vars": [
-			"error",
-			{ ignoreRestSiblings: true, argsIgnorePattern: "^_" },
+		'@typescript-eslint/no-empty-interface': 'off',
+		'@typescript-eslint/no-unused-vars': [
+			'error',
+			{ ignoreRestSiblings: true, argsIgnorePattern: '^_' },
 		],
 	},
-	settings: {
-		react: {
-			version: "detect",
-		},
-	},
-}
+};

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,36 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: "[BUG]"
+title: '[BUG]'
 labels: bug
 assignees: ''
-
 ---
 
-**Describe the bug**
-A clear and concise description of what the bug is.
+**Describe the bug** A clear and concise description of what the bug is.
+
+**To Reproduce** Steps to reproduce the behavior:
 
-**To Reproduce**
-Steps to reproduce the behavior:
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
 
-**Expected behavior**
-A clear and concise description of what you expected to happen.
+**Expected behavior** A clear and concise description of what you expected to
+happen.
 
-**Screenshots**
-If applicable, add screenshots to help explain your problem.
+**Screenshots** If applicable, add screenshots to help explain your problem.
 
 **Desktop (please complete the following information):**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
 
 **Smartphone (please complete the following information):**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
 
-**Additional context**
-Add any other context about the problem here.
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
+
+**Additional context** Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -4,17 +4,16 @@ about: Suggest an idea for this project
 title: ''
 labels: enhancement
 assignees: ''
-
 ---
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+**Is your feature request related to a problem? Please describe.** A clear and
+concise description of what the problem is. Ex. I'm always frustrated when [...]
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+**Describe the solution you'd like** A clear and concise description of what you
+want to happen.
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+**Describe alternatives you've considered** A clear and concise description of
+any alternative solutions or features you've considered.
 
-**Additional context**
-Add any other context or screenshots about the feature request here.
+**Additional context** Add any other context or screenshots about the feature
+request here.

.github/ISSUE_TEMPLATE/security_report.yml

@@ -5,7 +5,12 @@ labels: security
 body:
   - type: markdown
     attributes:
-      value: Thank you for taking the time to file a security report. We appreciate your feedback and contributions to this repository. However, before submitting, please make sure you can fill out all the details below in the template. If your issue is a "how to" or feature enhancement discussion, please go to the discussions tab and submit there instead.
+      value:
+        Thank you for taking the time to file a security report. We appreciate
+        your feedback and contributions to this repository. However, before
+        submitting, please make sure you can fill out all the details below in
+        the template. If your issue is a "how to" or feature enhancement
+        discussion, please go to the discussions tab and submit there instead.
   - type: textarea
     attributes:
       label: Identified Issue
@@ -15,4 +20,6 @@ body:
   - type: textarea
     attributes:
       label: Additional Information
-      description: Any additional information you think might be helpful to resolve your issue.
+      description:
+        Any additional information you think might be helpful to resolve your
+        issue.

.github/custom-issue-templates/content/0. Technology learning.md

@@ -2,14 +2,21 @@
 
 ## Background
 
-Many of the technologies we are using to build are cutting-edge or newer frameworks and individual developer experience will vary. It is important before commencing work on framework.dev that each developer spend some time getting familiar with the technology stack they will be working with. 
+Many of the technologies we are using to build are cutting-edge or newer
+frameworks and individual developer experience will vary. It is important before
+commencing work on framework.dev that each developer spend some time getting
+familiar with the technology stack they will be working with.
 
 ## Acceptance
 
-
-- [ ] Spend some time searching the internet, framework website, Twitter/Discord for information about the technologies you will be working with
-- [ ] Research who are the key players for the frameworks or technologies you will be working with (i.e. founders, advocates, contributors, promoters, etc)
-- [ ] Learn about the updates and changes to the framework or technology and some of the major features they solve
+- [ ] Spend some time searching the internet, framework website, Twitter/Discord
+      for information about the technologies you will be working with
+- [ ] Research who are the key players for the frameworks or technologies you
+      will be working with (i.e. founders, advocates, contributors, promoters,
+      etc)
+- [ ] Learn about the updates and changes to the framework or technology and
+      some of the major features they solve
 
 NOTE:
+
 - This task is timeboxed to 8 hours.

.github/custom-issue-templates/content/Add content for Blog.md

@@ -2,14 +2,16 @@
 
 ## Background
 
-As a visitor of the framework specific Framework.dev site I would like to have the ability to see enough Blog content to keep me informed and find this site to be resourceful and useful.
+As a visitor of the framework specific Framework.dev site I would like to have
+the ability to see enough Blog content to keep me informed and find this site to
+be resourceful and useful.
 
 ## Acceptance
 
-
 - [ ] Research a list of Blogs (at least 8-10 blogs)
 - [ ] Add the blog information in the data files
 - [ ] Test each individual look and external link
 
 NOTE:
+
 - This task is timeboxed to a maximum of 4 hours.

.github/custom-issue-templates/content/Add content for Books.md

@@ -2,15 +2,17 @@
 
 ## Background
 
-As a visitor of the framework specific Framework.dev site I would like to have the ability to see enough Books content to keep me informed and find this site to be resourceful and useful.
+As a visitor of the framework specific Framework.dev site I would like to have
+the ability to see enough Books content to keep me informed and find this site
+to be resourceful and useful.
 
 ## Acceptance
 
-
 - [ ] Research a list of Books
 - [ ] Add the Books information in the data files
 - [ ] Test each individual look and external link
 
 NOTE:
+
 - This task is timeboxed to a maximum of 4 hours.
-- O'Really is a very good resource for this.
+- O'Really is a very good resource for this.

.github/custom-issue-templates/content/Add content for Communities.md

@@ -2,19 +2,22 @@
 
 ## Background
 
-As a visitor of the framework specific Framework.dev site I would like to have the ability to see enough Communities content to keep me informed and find this site to be resourceful and useful.
+As a visitor of the framework specific Framework.dev site I would like to have
+the ability to see enough Communities content to keep me informed and find this
+site to be resourceful and useful.
 
 This should include:
+
 - Slack, discord, reddit
 - Conferences (not the actual dates, just the conference sites)
 - Meetup (not the actual dates)
 
 ## Acceptance
 
-
 - [ ] Research a list of Communities
 - [ ] Add the Communities information in the data files
 - [ ] Test each individual look and external link
 
 NOTE:
+
 - This task is timeboxed to a maximum of 4 hours.

.github/custom-issue-templates/content/Add content for Courses.md

@@ -2,14 +2,16 @@
 
 ## Background
 
-As a visitor of the framework specific Framework.dev site I would like to have the ability to see enough Courses content to keep me informed and find this site to be resourceful and useful.
+As a visitor of the framework specific Framework.dev site I would like to have
+the ability to see enough Courses content to keep me informed and find this site
+to be resourceful and useful.
 
 ## Acceptance
 
-
 - [ ] Research a list of Courses
 - [ ] Add the Courses information in the data files
 - [ ] Test each individual look and external link
 
 NOTE:
+
 - This task is timeboxed to a maximum of 4 hours.

.github/custom-issue-templates/content/Add content for Libraries.md

@@ -2,9 +2,12 @@
 
 ## Background
 
-As a visitor of the framework specific Framework.dev site I would like to have the ability to see enough Libraries content to keep me informed and find this site to be resourceful and useful.
+As a visitor of the framework specific Framework.dev site I would like to have
+the ability to see enough Libraries content to keep me informed and find this
+site to be resourceful and useful.
 
 Libraries have to be split into
+
 - State management
 - Data Fetching
 - Styling
@@ -15,10 +18,11 @@ Libraries have to be split into
 
 ## Acceptance
 
-
-- [ ] Research a list of Libraries and try to find at least ONE entry for each category.
+- [ ] Research a list of Libraries and try to find at least ONE entry for each
+      category.
 - [ ] Add the Libraries information in the data files
 - [ ] Test each individual look and external link
 
 NOTE:
+
 - This task is timeboxed to a maximum of 8 hours.

.github/custom-issue-templates/content/Add content for Podcasts.md

@@ -2,14 +2,16 @@
 
 ## Background
 
-As a visitor of the framework specific Framework.dev site I would like to have the ability to see enough Podcasts content to keep me informed and find this site to be resourceful and useful.
+As a visitor of the framework specific Framework.dev site I would like to have
+the ability to see enough Podcasts content to keep me informed and find this
+site to be resourceful and useful.
 
 ## Acceptance
 
-
 - [ ] Research a list of Podcasts
 - [ ] Add the Podcasts information in the data files
 - [ ] Test each individual look and external link
 
 NOTE:
+
 - This task is timeboxed to a maximum of 4 hours.

.github/custom-issue-templates/content/Add content for Tools.md

@@ -2,14 +2,18 @@
 
 ## Background
 
-As a visitor of the framework specific Framework.dev site I would like to have the ability to see enough Tools content to keep me informed and find this site to be resourceful and useful. Tools are softwares, browser and IDE extension aimed at supporting the development experience on this specific framework and it does not refeer to libraries.
+As a visitor of the framework specific Framework.dev site I would like to have
+the ability to see enough Tools content to keep me informed and find this site
+to be resourceful and useful. Tools are softwares, browser and IDE extension
+aimed at supporting the development experience on this specific framework and it
+does not refeer to libraries.
 
 ## Acceptance
 
-
 - [ ] Research a list of Tools
 - [ ] Add the Tools information in the data files
 - [ ] Test each individual look and external link
 
 NOTE:
+
 - This task is timeboxed to a maximum of 4 hours.

.github/custom-issue-templates/new-site/0. Setup local machine.md

@@ -2,7 +2,8 @@
 
 ## Background
 
-As a developer I would like a version of framework.dev to be setup and working on my local machine, so that I can develop my tasks.
+As a developer I would like a version of framework.dev to be setup and working
+on my local machine, so that I can develop my tasks.
 
 ## Acceptance
 
@@ -11,4 +12,5 @@ As a developer I would like a version of framework.dev to be setup and working o
 
 ## Notes:
 
-This task need to be completed by all members of the team, so it should be duplicated accordingly.
+This task need to be completed by all members of the team, so it should be
+duplicated accordingly.

.github/custom-issue-templates/new-site/1. Create basic folder and files.md

@@ -2,12 +2,17 @@
 
 ## Background
 
-As a developer I would like to initialize my framework.dev specific framework site so that the rest of the team and contributor can add content to make it useful for the wider community.
+As a developer I would like to initialize my framework.dev specific framework
+site so that the rest of the team and contributor can add content to make it
+useful for the wider community.
 
 ## Acceptance
 
 - [ ] Add all Data files
-- [ ] Add all Script required for development and production release in package.json
+- [ ] Add all Script required for development and production release in
+      package.json
 
 ## Notes:
-- This ticket is NOT going to tackle the addition of the current site on amplify. This is going to be handled by another ticket.
+
+- This ticket is NOT going to tackle the addition of the current site on
+  amplify. This is going to be handled by another ticket.