This repository was archived by the owner on Aug 25, 2025. It is now read-only.
Update "Usage" section to mention project name#70
Conversation
`npm init wasm-app` apparently fails without a project name given. See issue #44.
|
I believe the project name is optional. Perhaps it should be: |
Member
|
it is not currently optional! (tho i feel that perhaps it should be.) thanks for this PR! |
ashleygwilliams
approved these changes
Aug 21, 2019
|
Looking at the code, lines 6-13 of This code means that if the argument is omitted then Am I looking at the wrong file or branch? |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
npm init wasm-appapparently fails without a project name given. See issue #44.