VSinerva/freesewing
1
0
Fork 0
Code Activity
freesewing/packages/config-helpers/package.json

49 lines
1.4 KiB
JSON
Raw Normal View History

feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
{
feat(config-helpers): Renamed snapseries to config-helpers It would be useful to have a place where we can place methods like the pctBasedOn method that we now import from core, even though it has nothing to do with core. So I've decided to rename this packet since it's essentially also things that facilitate pattern configuration (files). Since this is a very new package, and I am 100% certain that we (FreeSewing itself) are the only ones using it, no need to major bump this. The most recent snapseries package will remain available for people who want to use it. I'll update all patterns accordingly.
2022-06-12 23:49:52 +02:00
"name": "@freesewing/config-helpers",
chore: develop now hosts v3 code
2022-08-23 13:45:20 +02:00
"version": "3.0.0-alpha.0",
feat(config-helpers): Renamed snapseries to config-helpers It would be useful to have a place where we can place methods like the pctBasedOn method that we now import from core, even though it has nothing to do with core. So I've decided to rename this packet since it's essentially also things that facilitate pattern configuration (files). Since this is a very new package, and I am 100% certain that we (FreeSewing itself) are the only ones using it, no need to major bump this. The most recent snapseries package will remain available for people who want to use it. I'll update all patterns accordingly.
2022-06-12 23:49:52 +02:00
"description": "A FreeSewing package to facilitate pattern configurations",
feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
"author": "Joost De Cock <joost@joost.at> (https://github.com/joostdecock)",
"homepage": "https://freesewing.org/",
"repository": "github:freesewing/freesewing",
"license": "MIT",
"bugs": {
"url": "https://github.com/freesewing/freesewing/issues"
},
"funding": {
"type": "individual",
"url": "https://freesewing.org/patrons/join"
},
"keywords": [
"freesewing",
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
"freesewing"
feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
],
chore(config-helpers): Migrated to esbuild & removed legacy devenv
2022-06-14 13:09:08 +02:00
"main": "dist/index.js",
chore: Remove rollup and legacy devenv dependencies
2022-06-14 14:00:43 +02:00
"module": "dist/index.mjs",
feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
"scripts": {
feat(config-helpers): Renamed snapseries to config-helpers It would be useful to have a place where we can place methods like the pctBasedOn method that we now import from core, even though it has nothing to do with core. So I've decided to rename this packet since it's essentially also things that facilitate pattern configuration (files). Since this is a very new package, and I am 100% certain that we (FreeSewing itself) are the only ones using it, no need to major bump this. The most recent snapseries package will remain available for people who want to use it. I'll update all patterns accordingly.
2022-06-12 23:49:52 +02:00
"build": "node build.js",
chore: Remove rollup and legacy devenv dependencies
2022-06-14 14:00:43 +02:00
"clean": "rimraf dist",
"mbuild": "NO_MINIFY=1 node build.js",
"symlink": "mkdir -p ./node_modules/@freesewing && cd ./node_modules/@freesewing && ln -s -f ../../../* . && cd -",
feat(config-helpers): Renamed snapseries to config-helpers It would be useful to have a place where we can place methods like the pctBasedOn method that we now import from core, even though it has nothing to do with core. So I've decided to rename this packet since it's essentially also things that facilitate pattern configuration (files). Since this is a very new package, and I am 100% certain that we (FreeSewing itself) are the only ones using it, no need to major bump this. The most recent snapseries package will remain available for people who want to use it. I'll update all patterns accordingly.
2022-06-12 23:49:52 +02:00
"test": "echo \"config-helpers: No tests configured. Perhaps you'd like to do this?\" && exit 0",
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
"vbuild": "VERBOSE=1 node build.js",
feat: Let yarn lab start the dev env
2022-06-17 14:12:46 +02:00
"lab": "cd ../../sites/lab && yarn start",
chore: Added scripts to facilitate development
2022-06-17 18:23:17 +02:00
"tips": "node ../../scripts/help.mjs",
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
"cibuild_step0": "node build.js"
feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
},
chore: Reconfigure packages
2022-05-21 20:34:32 +02:00
"peerDependencies": {},
"dependencies": {},
"devDependencies": {},
feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
"files": [
"dist/*",
chore: Reconfigure packages
2022-06-22 15:59:13 +02:00
"README.md"
feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
],
"publishConfig": {
"access": "public",
chore: develop now hosts v3 code
2022-08-23 13:45:20 +02:00
"tag": "next"
feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
},
"engines": {
feat(config-helpers): Renamed snapseries to config-helpers It would be useful to have a place where we can place methods like the pctBasedOn method that we now import from core, even though it has nothing to do with core. So I've decided to rename this packet since it's essentially also things that facilitate pattern configuration (files). Since this is a very new package, and I am 100% certain that we (FreeSewing itself) are the only ones using it, no need to major bump this. The most recent snapseries package will remain available for people who want to use it. I'll update all patterns accordingly.
2022-06-12 23:49:52 +02:00
"node": ">=14.0.0",
feat(snapseries): Initial release
2021-09-28 19:28:11 +02:00
"npm": ">=6"
}
}
Copy permalink