-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create 0001-non-usage-of-gatsby.rst (#12)
- Loading branch information
Adam Butterworth
authored
Oct 7, 2019
1 parent
1336ac1
commit a15b795
Showing
1 changed file
with
37 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
1. Non-Usage of Gatsby | ||
---------------------- | ||
|
||
Status | ||
------ | ||
|
||
Accepted | ||
|
||
Context | ||
------- | ||
|
||
This package is responsible for containing common code concerning the transpilation, | ||
building, linting, and testing of React-based microfrontends. Gatsby was considered as a | ||
potential tool for this job. | ||
|
||
Decision | ||
-------- | ||
|
||
We will not use Gatsby in these frontend build tools for two reasons: | ||
|
||
- Gatsby is itself a javascript framework. It concerns itself with more than | ||
frontend build tooling, including patterns and tools for the runtime of the frontend app itself. | ||
- Gatsby relies heavily on convention, expecting to find files in particular places. | ||
This makes it difficult/impossible to pull a common configuration of Gatsby into a | ||
package like this one. | ||
|
||
Consequences | ||
------------ | ||
|
||
Gatsby is a great tool for us leverage when appropriate, but it is not the right tool | ||
for the concern of this package. | ||
|
||
References | ||
---------- | ||
|
||
* https://www.gatsbyjs.org/docs/ | ||
* https://www.gatsbyjs.org/docs/gatsby-project-structure/ |