![]() Recently I refactored the prebuild code. One thing I did not touch (yet) was the various site dependencies. They were then ported to NX over the previous system with build priorities we had in place. And while that was a welcome improvement, it did not really address the bigger picture: we don't actually need to build any of these dependencies to build the site. All we need to do is help NodeJS so it can resolve everything from the source. So this commit does that by adding a top-level run script `yarn buildsiteconfigure` which calls `yarn reconfigure` but with the BUILDSITE variable set. When that variable is set, the reconfigure script will skip all optional steps and generate a slightly different package.json file that tells NodeJS to looks the package from source, rather than to look for the build files. After running this script, the prebuild step for the various sites will run without problems, even on a fresh repo where nothing has ever been build. So I've updated the prebuild script in the sites to run this. For local development, please use `uyarn predev` so that you don't muck with all the package.json files. If you do so (by accident or not) a `yarn reconfigure` run will put everything back in its place. |
||
---|---|---|
.github | ||
.husky | ||
ansible | ||
artwork | ||
config | ||
designs | ||
markdown | ||
media | ||
packages | ||
plugins | ||
scripts | ||
sites | ||
tests | ||
.all-contributorsrc | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.cjs | ||
.gitignore | ||
.gitpod.yml | ||
.npmrc | ||
.nvmrc | ||
.prettierignore | ||
.remarkrc.yaml | ||
.tool-versions | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
commitlint.config.js | ||
CONTRIBUTING.md | ||
CONTRIBUTORS.md | ||
crowdin.yml | ||
example.env | ||
LATEST_NEWS.md | ||
lerna.json | ||
LICENSE | ||
nx.json | ||
package.json | ||
README.md | ||
yarn.lock |
What am I looking at? 🤔
This repository is our monorepo holding all our NPM designs, plugins, other NPM packages, and (web)sites.
We are working on FreeSewing v3 🚀
We the
main
branch andnext
packages on NPM holds v3 code. But it's alpha for now.
The default branch (develop
) in this repo is where we work on the upcoming FreeSewing v3.
Check out the roadmap to
see what we're working towards. There is still time to submit your ideas/suggestions for
what you would like to see in our mext major release.
The current production code -- what is running on freesewing.org -- is in the v2
branch.
Getting started ⚡
As this is a monorepo. You'll need NodeJS v18, lerna and yarn on your system.
Once you have those, clone (or fork) this repo and run yarn kickstart
:
git clone git@github.com:freesewing/freesewing.git
cd freesewing
yarn kickstart
About FreeSewing 💀
Where the world of makers and developers collide, that's where you'll find FreeSewing.
If you're a maker, checkout freesewing.org where you can generate our sewing patterns adapted to your measurements.
If you're a developer, our documentation is on freesewing.dev. Our core library is a batteries-included toolbox for parametric design of sewing patterns. But we also provide a range of plugins that further extend the functionality of the platform.
If you have NodeJS installed, you can try it right now by running:
npx create-freesewing-pattern
Or, consult our getting started guides for Linux, MacOS, or Windows.
We also have a pattern design tutorial that walks you through your first parametric design, and a friendly community with people who can help you when you get stuck.
Support FreeSewing: Become a patron 🥰
FreeSewing is an open source project run by a community, and financially supported by our patrons.
If you feel what we do is worthwhile, and you can spend a few coind without hardship, then you should join us and become a patron.
Links 👩💻
- 💻 Makers website: freesewing.org
- 💻 Developers website: freesewing.dev
- 💬 Chat: On Discord via discord.freesewing.org
- ✅ Todo list/Kanban board: On Github via todo.freesewing.org
- 🐦 Twitter: @freesewing_org
- 📷 Instagram: @freesewing_org
License: MIT 🤓
© Joost De Cock.
See the license file for details.
Where to get help 🤯
Our chatrooms on Discord are the best place to ask questions, share your feedback, or just hang out.
If you want to report a problem, please create an issue.
Contributors ✨
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!