Refer to the CHANGELOG for all info.
---------
Co-authored-by: Wouter van Wageningen <wouter.vdub@yahoo.com>
Co-authored-by: Josh Munic <jpmunic@gmail.com>
Co-authored-by: Jonathan Haas <haasjona@gmail.com>
As reported in #2605 there's a broken link in the README's that points
to an old overview of all published packages on freesewing.dev.
Since we migrated to NextJS that page no longer exists, futhermore we've
moved away from the single `packages` workspace and now have one for
`packages`, `designs`, `plugins`, and `sites`. So I've just dropped the
link and rephrased the sentence.
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*.
This suppresses a warning in webpack v5 when importing the
version from the package.json file like a named export.
This use to be fine in webpack v4 but in v5 it's deprecated to
be more inline with the way it works in NodeJS.
That being said, it's very usefull as there's no need to pull in
the entire package.json file.
Futhermore, esbuild supports this out of the box so we also use
it in our build scripts.
So for now I'm supressing this warning. In FreeSewing v3 we'll
re-evaluate this.
