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

Create package.json for new components in pre-release step #574

Merged
merged 3 commits into from
Mar 7, 2018
Merged

Create package.json for new components in pre-release step #574

merged 3 commits into from
Mar 7, 2018

Commits on Mar 7, 2018

  1. Add check for any new component's package.json 

    If a new component has been added to src it needs a package.json file
when it gets copied to packages/

We use to do this manually and our tests that run after `build:packages`
task would fail.

With this script, when `npm run pre-release` is run, the script will
check if any new folders exist in packages after the copy task. If so,
it will create a sample package.json file with actual component name,
version 0.0.0 and latest version of globals as dependency.

It will also remind the developer to amend ALL/package.json file with
new dependencies.

When developer indicates they have done the above, the script will
and the rest of the `npm run pre-release` tasks will run.
    Jani Kraner committed Mar 7, 2018
    Configuration menu
    Copy the full SHA
    5da5d30 View commit details
    Browse the repository at this point in the history

  2. Update publishing docs to document updated flow

    Jani Kraner committed Mar 7, 2018
    Configuration menu
    Copy the full SHA
    9b77955 View commit details
    Browse the repository at this point in the history

  3. Document in CHANGELOG

    Jani Kraner committed Mar 7, 2018
    Configuration menu
    Copy the full SHA
    e3ce1e0 View commit details
    Browse the repository at this point in the history