[Meteor 3 - Feature]: Meteor create uses git instead of vendorized#12697
Merged
Grubba27 merged 13 commits intorelease-3.0from Jul 4, 2023
Merged
[Meteor 3 - Feature]: Meteor create uses git instead of vendorized#12697Grubba27 merged 13 commits intorelease-3.0from
Grubba27 merged 13 commits intorelease-3.0from
Conversation
|
This pull request has been linked to Shortcut Story #141: Meteor create <GIT_URL>. |
Collaborator
|
As much interesting as this is, I don't think this should be worked at least till after 3.0 is released. |
Contributor
Author
|
Probably will be launched together or a little bit later on, and IMO is an easy win for us in the team being able to change and update the skeletons and even add more without having to make a new whole release |
henriquealbert
approved these changes
Jul 3, 2023
Merged
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Under devolvement and discussion.
There are a few open topics I'm open to suggestions.
Meteor create changes
Today, when we use
meteor create <app>we use a static asset that is within the tool itself. In my proposal, I want to change how this works, there are a few reasons:Meteor create --example "exampleapp"
Would instead of just list and show how to clone, it would clone it and make it ready for your development.
Meteor create --from "https://github.com/meteor/skel-react"
Creates from a based URL, clones from that repo, and then initiates the project with the current meteor.
Cons?
prototypeapp(create with theinsecurepackages) it would continue to exist and people can opt-in. I think we(Core Meteor members) should be more opinative on a few things and this is one of them.Todo
Missing repos:
create skel-apollo
create skel-full
create skel-solid
create skel-vue
create skel-bare
create skel-minimal
create skel-svelte
create skel-vue-2
create skel-blaze
create skel-tailwind
create skel-chakra-ui
create skel-react
create skel-typescript
Create CDN repository (live here, will have it in a git)
Update docs(new option and ask the user to have git installed)
Open topics
git cloneandrm .git?)