https://github.com/jankapunkt/meteor-migration-helper

Detect which parts of your Meteor.js server environment need to be migrated in your current 2.x code.
https://github.com/jankapunkt/meteor-migration-helper

meteor meteor-3 meteor-package migration

Last synced: 2 months ago
JSON representation

Detect which parts of your Meteor.js server environment need to be migrated in your current 2.x code.

• Host: GitHub
• URL: https://github.com/jankapunkt/meteor-migration-helper
• Owner: jankapunkt
• License: mit
• Created: 2023-10-19T10:15:10.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-06-04T06:38:49.000Z (about 1 year ago)
• Last Synced: 2025-03-26T00:11:16.106Z (3 months ago)
• Topics: meteor, meteor-3, meteor-package, migration
• Language: JavaScript
• Homepage:
• Size: 13.7 KB
• Stars: 7
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Meteor.js Migration Helper

Detect which parts of your Meteor.js server environment need to be

migrated in your current 2.x code.

[![built with Meteor](https://img.shields.io/badge/Meteor-package-green?logo=meteor&logoColor=white)](https://packosphere.com/jkuester/migration-helper)

[![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

[![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#active)

No need to upgrade to 3.0 now to find out, what's still using Fibers.

There is also an article, which covers this packages functionality:

https://dev.to/jankapunkt/prepare-your-meteorjs-project-for-the-big-30-release-14bf

## Installation

```shell

$ meteor add jkuester:migration-helper

```

Now open in your Meteor.js project the file `.meteor/packages`

and move the entry `jkuester:migration-helper` to the top, in order

to also detect dependency packages that still use Fibers.

## Run detection

This is a runtime detection. In order to cover all detectable 

structures you need to either run your Meteor.js application

or the tests.

The more your tests cover of your code (test-coverage),

the better you will be able to detect these.

## Detect validated methods using mixins

This package also provides a mixin to be used

with `mdg:validated-method` 

You can import it via

```js

import { checkAsyncMixin } from 'meteor/jkuester:migration-helper'

// ...

const m = new ValidatedMethod({

  name: 'coolMethod',

  mixins: [checkAsyncMixin],

  validate: () => {},

  run: () => {}

})

```

A more versatile approach is to use a factory function for your ValidatedMethods:

```js

export const createMethod = options => {

  options.mixins = options.mixins ?? []

  options.mixins.push(checkAsyncMixin)

  return new ValidatedMethod(options)

}

```

If this is not feasible then you might skip this and let the package detect

them at runtime, when they are executed.

## Note

This package may not detect everything. However, it helps

to identify lots of parts on the server that need change and I hope

it will be useful to you.

## License

MIT