feat: replace webpack with esbuild (100s → 2.3s builds)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**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.
+
+**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]
+
+**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.

.github/ISSUE_TEMPLATE/epic-template.md

@@ -0,0 +1,29 @@
+---
+name: Epic Template
+about: For high-level, related sets of features and journeys.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Problem
+What problem are we solving with? Is this epic part of the planned features [here](https://github.com/near/near-wallet-roadmap/projects/1), and which ones?
+
+## How did we discover this problem?
+How did this problem originate? If it was revealed through user feedback, how was that feedback received and from whom?
+
+## Job Story(s)
+- What are the [job stories](https://thoughtbot.com/blog/converting-to-jobs-stories) that frame the users' context, motivations and goals?
+- Template: When I [situation], I want to [motivation] so I can [outcome/benefit].
+
+## What are we planning to do about it?
+- What is the scope of the design and engineering work required for this project?
+Along the way, this epic will be linked with issues and pull requests
+
+## What are we not planning to do about it?
+- What items have been considered but may fall out of the scope of design and engineering work for this project?
+Sometimes the scope is too large, and this section may lead other epics, other features [here](https://github.com/near/near-wallet-roadmap/projects/1) or even other products
+
+## How will we measure success?
+- Are there a set of quantifiable metrics that we can surface once the work has been completed in order to determine how successful our solution was?

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+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 [...]
+
+**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.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/user-story-template.md

@@ -0,0 +1,26 @@
+---
+name: User Story Template
+about: This template provides a basic structure for user stories.
+title: "Broad Set Template"
+labels: user-story
+assignees: ''
+
+---
+
+# User story
+Role: As a ....
+Ability: I want...
+Rationale: so that I can...
+
+*Add links to PRDs where applicable*
+
+# Acceptance criteria
+
+- [ ] This is something that can be verified to show that this user story is satisfied.
+
+# Sprint Ready Checklist 
+1. - [ ] Acceptance criteria defined 
+2. - [ ] Team understands acceptance criteria 
+3. - [ ] Team has defined solution / steps to satisfy acceptance criteria 
+4. - [ ] Acceptance criteria is verifiable / testable 
+5. - [ ] External / 3rd Party dependencies identified