npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@cosmotech/migrate-azure-sample-webapp

v0.2.1

Published

Scripts to help migrating between versions of the Azure Sample Webapp

Downloads

16

Readme

Azure Sample Webapp - Migration scripts

This folder contains migration scripts to help users migrate between major versions of the Azure Sample Webapp. These scripts can not guarantee a full coverage of the manual operations required when switching to a new major version, but they can automate some parts of the migration.

| :exclamation: Before running these scripts, please make sure you don't have uncommitted local changes in your webapp project. | | ----------------------------------------------------------------------------------------------------------------------------- |

This migration script requires Node 16 or above to run. If you don't already have this version, you can install it with:

nvm install 16
nvm use 16

Supported versions

Migrate from v2 to v3

npx @cosmotech/migrate-azure-sample-webapp v3

Migrate from v4 to v5

npx @cosmotech/migrate-azure-sample-webapp v5 [-s path/to/your/solution.yaml] [-w path/to/your/workspace.yaml]

Optional parameters:

  • -s/--solution: provide the path to an existing YAML solution description file to merge its content with your webapp configuration file src/config/ScenarioParameters.js and write the result in a new YAML file
  • -w/--workspace: provide the path to an existing YAML workspace description file to merge its content with your webapp configuration file src/config/PowerBI.js and write the result in a new YAML file

Dev notes

Run migration scripts from a local repository

  • cd to the folder containing the migration scripts (with files migrate.js and package.json) and run npm link
  • cd to the folder where you want to run the migration scripts, and run migrate-azure-sample-webapp v5

Release a new version of the migration script

For an official release:

npm version X.X.X --no-git-tag-version  # Replace X.X.X by the new version number
git add package.json
git commit -m "chore: bump migration script package version to X.X.X for release"  # Replace X.X.X here too
npm login
npm publish

For a non-official "dev" release:

npm version X.X.X-dev.X --no-git-tag-version  # Replace X.X.X-dev.X by the new version number
git add package.json
git commit -m "chore: bump migration script package version to X.X.X-dev.X for release"  # Replace X.X.X-dev.X here too
npm login
npm publish --tag dev