1
0
Fork 0
Commit graph

10 commits

Author SHA1 Message Date
Joost De Cock
322100f54c chore: Extended prettier for config files + run 2022-10-13 16:19:36 +02:00
Benjamin F
d7b0019373 Move snapseries to earlier build order. 2022-09-06 11:19:19 -07:00
Joost De Cock
ca59af12c6 chore: Remove unused import 2022-07-10 15:48:02 +02:00
Enoch Riese
69210d2296 change build order to have i18n last instead of package-info first 2022-07-03 18:38:18 -05:00
Enoch Riese
21eafa3347 don't build pattern-info twice 2022-07-03 18:33:42 -05:00
Enoch Riese
72c04edb15 isolate pattern-info in its own step 2022-07-02 21:00:53 -05:00
Enoch Riese
f8ec7c2cc9 trying to fix workflow with better build order 2022-07-02 20:37:37 -05:00
Joost De Cock
147920daeb fix: Updated to build order for extended designs 2022-06-16 18:05:44 +02:00
Joost De Cock
3c4beaead1 fix: Build order tweaks 2022-06-16 17:34:18 +02:00
Joost De Cock
e4035b2509 chore: Re-structure workspaces, enforce build order
These are some changes in the way the monorepo is structured,
that are aimed at making it easier to get started.

There are two important changes:

**Multiple workspaces**

We had a yarn workspaces setup at `packages/*`. But our monorepo has
grown to 92 packages which can be overwhelming for people not familiar
with the package names.

To remedy this, I've split it into 4 different workspaces:

- `designs/*`: Holds FreeSewing designs (think patterns)
- `plugins/*`: Holds FreeSewing plugins
- `packages/*`: Holds other packages published on NPM
- `sites/*`: Holds software that is not published as an NPM package,
  such as our various websites and backend API

This should make it easier to find things, and to answer questions like
*where do I find the code for the plugins*.

**Updated reconfigure script to handle build order**

One problem when bootstrapping the repo is inter-dependencies between
packages. For example, building a pattern will only work once
`plugin-bundle` is built. Which will only work once all plugins in the
bundle or built. And that will only work when `core` is built, and so
on.

This can be frustrating for new users as `yarn buildall` will fail.
And it gets overlooked by seasoned devs because they're likely to have
every package built in their repo so this issue doesn't concern them.

To remedy this, we now have a `config/build-order.mjs` file and the
updated `/scripts/reconfigure.mjs` script will enforce the build order
so that things *just work*.
2022-06-16 17:11:31 +02:00