Frontend Setup #27
Merged
Frontend Setup #27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Nukesor
force-pushed
the
frontend
branch
2 times, most recently
from
29d41c8
to
3291145
Compare
Closed
dasmerlon
requested changes
Nov 28, 2022
dasmerlon
approved these changes
Nov 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a basic frontend setup using several technologies:
Most of this stuff is pure boiler plate code.
The documentation to set all of this up together is super convoluted and quite confusing.
For this reason, I went with this template repository, checked how things were done and adjusted the configuration/project setup to our needs.