saojs/sao

Better way to add new dependencies in template's package.json

Open

#12 opened on Dec 31, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (1,049 stars) (63 forks)user submission
discussionhelp wanted

Description

package.json in templates is always messed up with template markups, so it's impossible to update it via yarn add

Contributor guide

Tech stack
typescriptnodejs
Domain
clitooling
Issue type
feature
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.
half day
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.
unclear
Prerequisites
Understanding of sao template syntaxNode.js and npm basicsPackage.json structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate how sao processes template files, particularly the package.json template. The repository likely has a 'templates' directory with files containing special markup. Understand the current mechanism and identify why 'yarn add' messes up the file. Propose a solution such as separating dependency definitions from the template or using a post generation script to handle dependencies. Look for any existing discussion or related issues in the repository (none currently). After understanding the template engine, implement a function to update package.json programmatically without interfering with template syntax.
Better way to add new dependencies in template's package.json · saojs/sao#12 | Good First Issue