meteor/meteor

[feature]: Vue 3 and Typescript flags should generates a vue + typescript project

Open

#12368 opened on Dec 13, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (44,781 stars) (5,257 forks)batch import
Type:Featureconfirmedgood first issueidlemissing-docs

Description

This meteor create --vue --typescript meteor-vue3-typescript results in a project with react dependencies not vue.

Meteor 2.9

Contributor guide

Tech stack
vuetypescript
Domain
clideveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Meteor CLI basicsVue 3TypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
The issue is in the meteor create command, specifically when combining vue and typescript flags. The relevant source code is in the packages/ directory of the Meteor repository, likely around the scaffolding logic that generates the initial project files. Start by examining the meteor create implementation in the CLI package, focusing on how the flags are parsed and how project templates (e.g., Vue vs React) are selected. Check the issue comments for any additional context or potential fix directions. Look at the generated package.json and dependencies to understand why React is being included instead of Vue.