Skip to content
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.

Sign up for GitHub

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

Jump to bottom

backtrack init needs to be ran twice with package.json updates #5

Open
chrisblossom opened this issue Jun 12, 2019 · 0 comments
Open

backtrack init needs to be ran twice with package.json updates #5

chrisblossom opened this issue Jun 12, 2019 · 0 comments
Labels
bug Something isn't working
Milestone
1.0.0

Comments

@chrisblossom
Copy link
Owner

chrisblossom commented Jun 12, 2019 •
edited

Possible solution: export named package.json object so before writing so plugins / packages can correctly read engines field etc without having to run backtrack init twice.
@chrisblossom chrisblossom added this to the 1.0.0 milestone Jun 12, 2019
@chrisblossom chrisblossom added enhancement New feature or request bug Something isn't working and removed enhancement New feature or request labels Jun 12, 2019
@chrisblossom chrisblossom changed the title export named package.json object backtrack init needs to be ran twice with package.json updates Jun 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@chrisblossom