Added v0.1.0 of create-nuxt3-app#2
Conversation
create-nuxt3-app and cn3a-plop-files packagescreate-nuxt3-app
create-nuxt3-appcreate-nuxt3-app
|
Successfully published first alpha version for testing: npx create-nuxt3-app@0.0.1-alpha.3Tests:
|
|
I tested it out with our PM @LukSteib, initial feedback and observations:
|
|
I implemented the requested changes: You can see the readme here: https://www.npmjs.com/package/create-nuxt3-app You can test the new messages with: |
|
|
||
| See more information about usage on the main [ReadMe](../../README.md). | ||
| [![npm version][npm-version-src]][npm-version-href] | ||
| [![npm downloads][npm-downloads-src]][npm-downloads-href] |
There was a problem hiding this comment.
this count is outdated!
please ctrl + shift + f and ensure that sidebase is replaced with create-nuxt3-app (:
There was a problem hiding this comment.
It should not be. I changed the values at the bottom of the ReadMe to reflect the correct repo!
| - Testing framework | ||
| - ViTest (currently included) | ||
|
|
||
| We are always looking for more options to include! Join in on the conversation [here](https://github.com/sidebase/sidebase/issues/70)! |
There was a problem hiding this comment.
maybe we can move that issue here / open a new one here and then reference the old one?
| "chalk": "^5.1.2", | ||
| "defu": "^6.1.0", | ||
| "fs-extra": "^10.1.0", | ||
| "node-plop": "^0.31.0", | ||
| "prompts": "^2.4.2" |
There was a problem hiding this comment.
please check if all of these are still actually used in the final package (:
There was a problem hiding this comment.
I do use all of them, however I (generally still) often wonder if I really need them as dependencies or if it is enough to include them as dev-dependencies.
On all of their installation pages they were being added as non dev-dependencies. Does that mean they need to be added regularly or can I check it another way?
| @@ -0,0 +1,231 @@ | |||
|  | |||
|  | |||
There was a problem hiding this comment.
Can we already make this less sidebase-y?
I would:
- remove most of the sidebase references
- then remove all assets that become irelevant (e.g. the .github/ pngs and svg that make this package big)
- link to the original sidebase for further documentation
- style this more like a scaffold / starter readme for a project
There was a problem hiding this comment.
Sure thing! I will actully do this a bit differently. I will make a new branch on sidebase/sidebase in which I will remove most of the branding. That way we can merge main into it whenever we update anything to make it easier in the future to upgrade the scaffold!
Closes #3
Contributes to sidebase/sidebase#59
I decided to not finish the
with-serveroption for release 0.1.0, as I am still struggling with a few issues that I will track in another issue. As discussed beforehand, we want to release an initial version to test the functionality after publishing, see how well it works and find any bugs we need to fix.Once we release this version we can begin focusing on adding new options (first being
with-server)