-
Notifications
You must be signed in to change notification settings - Fork 3
feat: add init command #206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: efab2cb The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some initial thoughts. I'm not too familiar with the Ferric stuff, so I defer to others.
packages/ferric-example/package.json
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's still handy to keep the ferric-example
around for reference (and development) even if adding a generate
command. Let's not delete this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was going to replace it with the app-test, to have it actually be consumed by it while having it in there. More of a real way to test.
init
command to generate / scaffold the project.ferric-example
withapp-test
, scaffolding the project there.Cargo.toml
optimizations for size. Reduce native files size #196Ideally merge #205 first.