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

strapi-plugin-migrate-data

v0.0.6

Published

This plugin is developed for migrating strapi version 3 data to strapi version 4 with swagger.

Downloads

3

Readme

You can move your strapi V3 data to V4 with the APIs that strapi has made available. In order to use the plugin, swagger must be used on both sides.

Swagger Install “V4”:

with npm:


npm install @strapi/plugin-documentation

with yarn:


yarn add @strapi/plugin-documentation

To apply the plugin to Strapi, a re-build is needed:


strapi build

To install swagger on the Strapi V3.

SETUP:

This plugin is developed for V4.

Add the package into your Strapi project:

with npm:


npm install strapi-plugin-merge-data

with yarn:


yarn add strapi-plugin-merge-data

After these steps Strapi should be re-built:


strapi build

Strapi should be run in the next step:


strapi start

// or

yarn start

The plugin works in Production mode. The above command runs Strapi in "Production" mode. This plugin does not support "Developer" mode.

GETTING STARTED:

When migrating from V3 to V4, the "find" and "count" apis in the corresponding table of V3 should be in the "public" role.

Selecting and adding tables

Open the "Settings" tab, enter the Swagger URL of V3 here and press the “Get Entity Model” button.

On the left, there is a table where tables of V4 can be selected, and on the right, tables from V3 can be selected.

After selecting the V3 table that corresponds to the table in V4, press OK and select the relevant columns. The values on the left show the columns of the selected table belonging to V4, and the values on the right show the columns of the selected table belonging to V3. We select the columns V3 that will correspond to the columns of the table selected in V4. Columns with the same names are automatically selected and can be edited if desired. After making all the selections, the "save selected" button at the bottom is pressed.

Additions are shown in the "collection" tab. If the "Clear Table" option is checked,all data in the relevant table is deleted before data transfer, and then data transfer starts. If there is a relationship between two tables, make sure that the mappings are correct. The data should be exported to V4 with the ID number in the V3 table. For this reason, before clicking the "relation transfer" button, you must have transferred the data of the related tables correctly, otherwise the relations will not be transferred. Another thing to consider is to make sure that data with the same credential does not already exist in version 4 before transferring the data. If data has been transferred with the same ID number before, the new data will not be transferred to V4. For all these reasons, it is recommended to transfer data to clean tables, otherwise relationships may be established incorrectly.

If there is a collection attached, it can be edited from the "settings" tab. "Save Change" button can be used to save changes. If it is desired to continue with a new Swagger, all collections can be deleted with the "Clear Collections" button atthe bottom.