Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
@almin/migration-tools
Advanced tools
Readme
Migration scripts for Almin.
Install with npm:
npm install -g @almin/migration-tools
Simply run almin-migration-tools
in your terminal and answer a few questions.
You can pass a filename directly to the CLI. If you do not, you will be prompted for one.
Ensure you have a backup of your source code or commit the latest changes before running this.
Usage
$ almin-migration-tools [<file|glob>]
Options:
--script Run with specified migration script
--dry-run Enable dry run mode
--force, -f Bypass safety checks and forcibly run codemods
Examples
# Interactive mode
$ almin-migration-tools
# Interactive mode, but it has default targets
$ almin-migration-tools "src/**/*.js"
# Non interactive mode, specified script name
$ almin-migration-tools --script "store-group-arguments" "src/**/store/**/*.js"
Run following command and select 0.17.x → 0.18.x
$ almin-migration-tools
executor()
is deprecated.
You should use UseCaseExecutor#execute
instead of UseCaseExecutor#executor
.
Before: executor()
import { UseCase, Context } from "almin";
class MyUseCaseA extends UseCase {
execute(_a: string) {}
}
const context = new Context({
store: createStore({ name: "test" })
});
// executor
context.useCase(new MyUseCaseA()).executor(useCase => useCase.execute("A"));
After: execute()
import { UseCase, Context } from "almin";
class MyUseCaseA extends UseCase {
execute(_a: string) {}
}
const context = new Context({
store: createStore({ name: "test" })
});
//execute
context.useCase(new MyUseCaseA()).execute("A");
Run following command and select 0.13.x → 0.15.x
$ almin-migration-tools
ChangedPayload
has been removed.
import { UseCase, ChangedPayload } from "almin";
export class ExampleUseCase extends UseCase {
execute() {
this.context.useCase(new ChangedPayload()).execute();
}
}
to
import { UseCase } from "almin";
export class ExampleUseCase extends UseCase {
execute() {
this.context.useCase({ type: "ChangedPayload" }).execute();
}
}
Run following command and select 0.12.x → 0.13.x
$ almin-migration-tools
context.on*
to context.events.on*
without context.onChange
Context.onChange
is still on Context
prototype.context.onWillExecuteEachUseCase((payload, meta) => {});
context.onDispatch((payload, meta) => {});
context.onDidExecuteEachUseCase((payload, meta) => {});
context.onCompleteEachUseCase((payload, meta) => {});
context.onErrorDispatch((payload, meta) => {});
to
context.events.onWillExecuteEachUseCase((payload, meta) => {});
context.events.onDispatch((payload, meta) => {});
context.events.onDidExecuteEachUseCase((payload, meta) => {});
context.events.onCompleteEachUseCase((payload, meta) => {});
context.events.onErrorDispatch((payload, meta) => {});
Notes: Sadly, this old migration script is not automated...
Please do following steps.
Target: Store files
# Install to global
npm install -g @almin/migration-tools
# Run migration scripts
## Target: your almin store files
almin-migration-tools --script "store-get-state-return-object-to-flat" "src/**/store/**/*.js"
Store#getState return value migration.
This script migrate following adn write stats to almin-store-state-mapping.json
.
Found Following pattern and replace
class MyStore extends Store {
getState() {
return {
stateName: state
}
}
}
to
class MyStore extends Store {
getState() {
return state;
}
}
This script output stats as almin-store-state-mapping.json
.
The almin-store-state-mapping.json
is used with next script(Convert StoreGroup constructor).
Target: StoreGroup file
# Install to global
npm install -g @almin/migration-tools
# Run migration scripts
## Target: your almin StoreGroup file
almin-migration-tools --script "store-group-arguments" "src/**/store/**/*.js"
Migrate StoreGroup constructor arguments.
This script migrate following using store-state-mapping.json
.
new StoreGroup([
new CartStore(cartRepository),
new CustomerStore(customerRepository),
new ProductStore(productRepository)
])
with
new StoreGroup({
"cart": new CartStore(cartRepository),
"customer": new CustomerStore(customerRepository),
"product": new ProductStore(productRepository)
});
mapping
: path to almin-store-state-mapping.json
.
almin-store-state-mapping.json
in current directory.See Releases page.
Install devDependencies and Run npm test
:
npm i -d && npm test
Pull requests and stars are always welcome.
For bugs and feature requests, please create an issue.
git checkout -b my-new-feature
git commit -am 'Add some feature'
git push origin my-new-feature
MIT © azu
FAQs
Migration scripts for Almin.
The npm package @almin/migration-tools receives a total of 2 weekly downloads. As such, @almin/migration-tools popularity was classified as not popular.
We found that @almin/migration-tools demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.