feat(init): use package.json & ECMA-419 in default project scaffold #199
Conversation
This file contains 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.
To streamline the getting started experience with embedded JS, this PR uses
package.jsonconfigured with the ECMA-419 APIs as the default project template forxs-dev init, instead of the minimalmanifest.jsonthat may be more familiar to Moddable developers. The relevant docs and guide have been updated based on this change as well.A
--manifestflag was added for developers who prefer to use that project configuration file instead.This PR also includes a fix for esp and windows setup targets.
📦 Published PR as canary version:
0.35.1--canary.199.f6ddf1a.0✨ Test out this PR locally via:
npm install xs-dev@0.35.1--canary.199.f6ddf1a.0 # or yarn add xs-dev@0.35.1--canary.199.f6ddf1a.0