You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I put --apply before the file glob, I get the following output:
> can-migrate --apply **/*.js
Codemods to simplify upgrading CanJS.
Usage
$ can-migrate [<file|glob> ...]
Updates files according to the CanJS 3.0 or CanJS 4.0 migration paths (minimal, modern, future)
More info for v3.0: http://canjs.github.io/canjs/doc/migrate-3.html#Modernizedmigrationpath
More info for v4.0: http://canjs.github.io/canjs/doc/migrate-4.html
Options
--apply -a Apply transforms (instead of a dry run)
--force Apply transforms regardless of git status
--silent -s Silence output
--config -c Path to custom config file
--transform -t specify a transform
--can-version specify CanJS version to upgrade to
Examples
can-migrate **/*.js
can-migrate --apply **/*.js
can-migrate -iad **/*.js
can-migrate **/*.* --transform can-route/register.js
can-migrate **/*.* --can-version 4
Putting --apply at the end of the command works around this issue. Either --apply should work in the way the help output describes, or the output should be updated to correctly reflect the requirements.
The text was updated successfully, but these errors were encountered:
If I put
--apply
before the file glob, I get the following output:Putting
--apply
at the end of the command works around this issue. Either--apply
should work in the way the help output describes, or the output should be updated to correctly reflect the requirements.The text was updated successfully, but these errors were encountered: