microsoft / microsoft/process-migrator
userSpecifiedMode.toLocaleLowerCase is not a function error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Using the latest versions of nodejs/npm/process-migrator, when attempting to import a custom process template we receive the below error when attempting to use the '-mode=' parameter with a properly formatted configuration.json
For example. process-migrator -mode=import --config='c:\temp\configuration.json'
When we use the process-migrator command without the '-mode=' parameter (which would default to migrate mode) and have a properly configured configuration.json we are able to successfully migrate a process from one devops org to another.
For example. process-migrator --config='c:\temp\configuration.json'
there appears to be some issue with main.js and ConfigurationProcessor.js
Error Below
C:\Users\root\AppData\Roaming\npm\node_modules\process-migrator\build\nodejs\nodejs\ConfigurationProcessor.js:31
switch (userSpecifiedMode.toLocaleLowerCase()) {
^
TypeError: userSpecifiedMode.toLocaleLowerCase is not a function
at Object.ProcesCommandLine (C:\Users\root\AppData\Roaming\npm\node_modules\process-migrator\build\nodejs\nodejs\ConfigurationProcessor.js:31:35)
at main (C:\Users\root\AppData\Roaming\npm\node_modules\process-migrator\build\nodejs\nodejs\main.js:18:57)
at Object. (C:\Users\root\AppData\Roaming\npm\node_modules\process-migrator\build\nodejs\nodejs\main.js:72:1)
at Module._compile (node:internal/modules/cjs/loader:1376:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
at Module.load (node:internal/modules/cjs/loader:1207:32)
at Module._load (node:internal/modules/cjs/loader:1023:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
at node:internal/main/run_main_module:28:49
Node.js v21.1.0
PS C:\Users\root>
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with build/nodejs/nodejs/ConfigurationProcessor.js and main.js, following how the -mode argument from process-migrator -mode=import --config=... is parsed before userSpecifiedMode.toLocaleLowerCase() runs. Reproduce the reported import command and verify that a properly configured template imports successfully while the no-mode migrate command continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100