RICEVIAMO E PUBBLICHIAMO – “Di Gregorio parla dei 55,2 milioni buttati da Regione Lombardia per un referendum consultivo, quando dimentica i 54 MILIARDI DI RESIDUO FISCALE che non rimangono sul territorio lombardo, bensì vanno a Roma”, Bonetti ...

Lega Magenta: “Di Gregorio del Pd, dichiarazioni inaccettabili. Studi meglio i numeri, anziché darli”

Torna mercoledì 1 novembre 2023 su viale Toselli a Legnano la tradizionale Fiera dei Morti. Saranno 170 i banchi che si distribuiranno lungo un tratto di quasi un chilometro fra via Santa Caterina e l

Fiera dei morti: in arrivo 170 bancarelle a Legnano

E’ una disciplina ancora considerata ad appannaggio di pochi appassionati. In realtà il Polo sta prendendo sempre più piede, tanto che in questo week end il Magenta Polo Club ha organizzato un torneo

Torneo amichevole con il Magenta Polo ASD, disciplina che piace sempre di più

La città di Magenta si appresta a vivere le celebrazioni del suo Santo patrono con un programma ricco di eventi

Tutto pronto per la Festa di San Martino

La donna, residente a Magenta, è molto conosciuta in città anche per via del suo impegno nel mondo del volontariato

Raffaella Mastaglia nominata Cavaliere all'Ordine al Merito della Repubblica Italiana

Il Comune di Magenta insieme alla libreria La Memoria del Mondo organizza la presentazione del libro di Loris Caruso dal titolo “In Campo la vita sparisce” dedicato al calciatore Diego Armando Maradon

Magenta: una serata dedicata al grande Diego Armando Maradona

E' stato condannato per la morte dell’operaio Umberto De Paola, 56enne di Magenta, deceduto dopo essere caduto da una scala sul posto di lavoro.

Cade da una scala e muore: in Appello condannato il datore di lavoro

Un atto di vandalismo che ha dell’incredibile quello commesso oggi allo stadio Comunale di Magenta. Mentre era in corso il match di cartello tra la squadra di casa e il Pavia 1911, probabilmente duran

Magenta Pavia, nell’intervallo ignoti sfondano il muro dello stadio. Indagano i Carabinieri

Una giornata dedicata alla prevenzione del tumore al seno con le visite senologiche in casa Giacobbe a Magenta. Evento organizzato da Salute Donna e Aicit, l’associazione intervento contro i tumori. Aicit ha appena concluso l’ordine di un ...

Prevenzione in Casa Giacobbe a Magenta, Aicit dona un ecografo a Salute Donna

Il 16enne volante di Magenta dopo una rimonta da sogno, grazie alla doppia vittoria ad Albenga si è laureato campione di Quad cross

Riccardo Lami è campione italiano di Quad cross

Magenta SRL

magentasrl

The Man in the Brown Suit by Agatha Christie, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . PROLOGUE PROLOGUE Nadina, the Russian dancer who had taken Paris by storm, swayed to the sound of the applause, bowed and bowed again. Her narrow black eyes narrowed themselves still more, the long line of her scarlet mouth curved faintly upwards. Enthusiastic Frenchmen continued to beat the ground appreciatively as the curtain fell with a swish, hiding the reds and blues and magentas of the bizarre décors. In a swirl of blue and orange draperies the dancer left the stage. A bearded gentleman received her enthusiastically in his arms. It was the Manager. “Magnificent, petite, magnificent,” he cried. “To-night you have surpassed yourself.” He kissed her gallantly on both cheeks in a somewhat matter-of-fact manner. Madame Nadina accepted the tribute with the ease of long habit and passed on to her dressing-room, where bouquets were heaped carelessly everywhere, marvellous garments of futuristic design hung on pegs, and the air was hot and sweet with the scent of the massed blossoms and with more sophisticated perfumes and essences. Jeanne, the dresser, ministered to her mistress, talking incessantly and pouring out a stream of fulsome compliment. A knock at the door interrupted the flow. Jeanne went to answer it, and returned with a card in her hand. “Madame will receive?” “Let me see.” The dancer stretched out a languid hand, but at the sight of the name on the card, “Count Sergius Paulovitch,” a sudden flicker of interest came into her eyes. “I will see him. The maize peignoir, Jeanne, and quickly. And when the Count comes you may go.” “Bien, Madame.” Jeanne brought the peignoir, an exquisite wisp of corn-coloured chiffon and ermine. Nadina slipped into it, and sat smiling to herself, whilst one long white hand beat a slow tattoo on the glass of the dressing-table. The Count was prompt to avail himself of the privilege accorded to him—a man of medium height, very slim, very elegant, very pale, extraordinarily weary. In feature, little to take hold of, a man difficult to recognize again if one left his mannerisms out of account. He bowed over the dancer’s hand with exaggerated courtliness. “Madame, this is a pleasure indeed.” So much Jeanne heard before she went out closing the door behind her. Alone with her visitor, a subtle change came over Nadina’s smile. “Compatriots though we are, we will not speak Russian, I think,” she observed. “Since we neither of us know a word of the language, it might be as well,” agreed her guest. By common consent, they dropped into English, and nobody, now that the Count’s mannerisms had dropped from him, could doubt that it was his native language. He had, indeed, started life as a quick-change music-hall artiste in London. “You had a great success to-night,” he remarked. “I congratulate you.” “All the same,” said the woman, “I am disturbed. My position is not what it was. The suspicions aroused during the War have never died down. I am continually watched and spied upon.” “But no charge of espionage was ever brought against you?” “Our chief lays his plans too carefully for that.” “Long life to the ‘Colonel,’” said the Count, smiling. “Amazing news, is it not, that he means to retire? To retire! Just like a doctor, or a butcher, or a plumber——” “Or any other business man,” finished Nadina. “It should not surprise us. That is what the ‘Colonel’ has always been—an excellent man of business. He has organized crime as another man might organize a boot factory. Without committing himself, he has planned and directed a series of stupendous coups, embracing every branch of what we might call his ‘profession.’ Jewel robberies, forgery, espionage (the latter very profitable in war-time), sabotage, discreet assassination, there is hardly anything he has not touched. Wisest of all, he knows when to stop. The game begins to be dangerous?—he retires gracefully—with an enormous fortune!” “H’m!” said the Count doubtfully. “It is rather—upsetting for all of us. We are at a loose end, as it were.” “But we are being paid off—on a most generous scale!” Something, some undercurrent of mockery in her tone, made the man look at her sharply. She was smiling to herself, and the quality of her smile aroused his curiosity. But he proceeded diplomatically: “Yes, the ‘Colonel’ has always been a generous paymaster. I attribute much of his success to that—and to his invariable plan of providing a suitable scapegoat. A great brain, undoubtedly a great brain! And an apostle of the maxim, ‘If you want a thing done safely, do not do it yourself!’ Here are we, every one of us incriminated up to the hilt and absolutely in his power, and not one of us has anything on him.” He paused, almost as though he were expecting her to disagree with him, but she remained silent, smiling to herself as before. “Not one of us,” he mused. “Still, you know, he is superstitious, the old man. Years ago, I believe, he went to one of these fortune-telling people. She prophesied a lifetime of success, but declared that his downfall would be brought about through a woman.” He had interested her now. She looked up eagerly. “That is strange, very strange! Through a woman, you say?” He smiled and shrugged his shoulders. “Doubtless, now that he has—retired, he will marry. Some young society beauty, who will disperse his millions faster than he acquired them.” Nadina shook her head. “No, no, that is not the way of it. Listen, my friend, to-morrow I go to London.” “But your contract here?” “I shall be away only one night. And I go incognito, like Royalty. No one will ever know that I have left France. And why do you think that I go?” “Hardly for pleasure at this time of year. January, a detestable foggy month! It must be for profit, eh?” “Exactly.” She rose and stood in front of him, every graceful line of her arrogant with pride. “You said just now that none of us had anything on the chief. You were wrong. I have. I, a woman, have had the wit and, yes, the courage—for it needs courage—to double-cross him. You remember the De Beer diamonds?” “Yes, I remember. At Kimberley, just before the war broke out? I had nothing to do with it, and I never heard the details, the case was hushed up for some reason, was it not? A fine haul too.” “A hundred thousand pounds worth of stones. Two of us worked it—under the ‘Colonel’s’ orders, of course. And it was then that I saw my chance. You see, the plan was to substitute some of the De Beer diamonds for some sample diamonds brought from South America by two young prospectors who happened to be in Kimberley at the time. Suspicion was then bound to fall on them.” “Very clever,” interpolated the Count approvingly. “The ‘Colonel’ is always clever. Well, I did my part—but I also did one thing which the ‘Colonel’ had not foreseen. I kept back some of the South American stones—one or two are unique and could easily be proved never to have passed through De Beer’s hands. With these diamonds in my possession, I have the whip-hand of my esteemed chief. Once the two young men are cleared, his part in the matter is bound to be suspected. I have said nothing all these years, I have been content to know that I had this weapon in reserve, but now matters are different. I want my price—and it will be a big, I might almost say a staggering price.” “Extraordinary,” said the Count. “And doubtless you carry these diamonds about with you everywhere?” His eyes roamed gently round the disordered room. Nadina laughed softly. “You need suppose nothing of the sort. I am not a fool. The diamonds are in a safe place where no one will dream of looking for them.” “I never thought you a fool, my dear lady, but may I venture to suggest that you are somewhat foolhardy? The ‘Colonel’ is not the type of man to take kindly to being blackmailed, you know.” “I am not afraid of him,” she laughed. “There is only one man I have ever feared—and he is dead.” The man looked at her curiously. “Let us hope that he will not come to life again, then,” he remarked lightly. “What do you mean?” cried the dancer sharply. The Count looked slightly surprised. “I only meant that a resurrection would be awkward for you,” he explained. “A foolish joke.” She gave a sigh of relief. “Oh, no, he is dead all right. Killed in the war. He was a man who once—loved me.” “In South Africa?” asked the Count negligently. “Yes, since you ask it, in South Africa.” “That is your native country, is it not?” She nodded. Her visitor rose and reached for his hat. “Well,” he remarked, “you know your own business best, but, if I were you, I should fear the ‘Colonel’ far more than any disillusioned lover. He is a man whom it is particularly easy to—underestimate.” She laughed scornfully. “As if I did not know him after all these years!” “I wonder if you do?” he said softly. “I very much wonder if you do.” “Oh, I am not a fool! And I am not alone in this. The South African mail-boat docks at Southampton to-morrow, and on board her is a man who has come specially from Africa at my request and who has carried out certain orders of mine. The ‘Colonel’ will have not one of us to deal with, but two.” “Is that wise?” “It is necessary.” “You are sure of this man?” A rather peculiar smile played over the dancer’s face. “I am quite sure of him. He is inefficient, but perfectly trustworthy.” She paused, and then added in an indifferent tone of voice: “As a matter of fact, he happens to be my husband.” About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Agatha Christie (2020). The Man in the Brown Suit. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/61168/pg61168-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org , located at https://www.gutenberg.org/policy/license.html.

Nadina, the Russian dancer

Command-line utilities are the most basic and beautiful apps ever created, the apps that started it all. We use command-line utilities every day, whether it be git, grep, awk, npm, or any other terminal app. CLIs are super useful and usually the fastest way to get something done. Do you have something in your specific workflow that you have to do over and over again? Chances are that can be automated with a CLI. We are going to use to make our CLI if it wasn’t clear from the title itself. Why? Because the Node.js ecosystem has thousands of extremely useful packages that we can utilize to achieve what we are trying to do. Whatever it may be that you are trying to do, it is highly probable that there exists a package for it on also node has built-in libraries to do a lot of things like Apart from that CLIs built in Node.js are , meaning they are easy to install on different OSs. Node.js npm, handling files, launching other applications, asserting tests, etc. highly portable For the purpose of this tutorial, we’ll be building a simple CLI to . We’ll accept string type arguments, parse them into a sentence, shoot them off to a translation API which will fetch us the translations, and then display the result. The complete code for this can be found on the . Let’s dive right into it! translate between languages Github repository Prerequisites Here are the tools that are required to make the CLI so make sure you have them before starting: A recent version of installed. Node.js A text editor. and that’s probably it. Setting up the project We’ll be setting up a basic Node.js project: 1. Open up your terminal. 2. Create a folder for the project. ~$mkdir termTranslate 3. Navigate to it. ~$cd termTranslate 4. Initialize a Node.js project in that folder. ~$npm init 5. Fill in the prompt. Your project is now set up. Building the basic CLI Now that we have our node project ready we move to actually making the CLI. Here’s what you have to do: 1. Create a folder named in the root directory of your project. bin 2. Inside create a file called This is going to be the entry point of our CLI. bin index.js 3. Now open the file and change the “main” part to . package.json bin/index.js 4. Now manually add another entry into the file called bin and set it’s key to and it’s value to . The addition should look something like this: package.json tran ./bin/index.js : { : } "bin" "tran" "./bin/index.js" The key, , is the . This is the keyword that people will type in the terminal for using your CLI. Be free to name it whatever you like, although I would suggest keeping the name short and semantic so that it’s quick to type and easy to remember. tran keyword for calling the CLI The name defined here is and can be changed whenever you like. not permanent Your entire file should look something like this: package.json { : , : , : , : , : { : }, : [ ], : { : }, : , : } "name" "termtran" "version" "1.0.0" "description" "A CLI to translate between languages in the terminal" "main" "bin/index.js" "scripts" "test" "echo \"Error: no test specified\" && exit 1" "keywords" "cli" "bin" "tran" "./bin/index.js" "author" "Your Name" "license" "ISC" Don’t forget to add the extra comma after adding the new entry into the file. That is an easy mistake. Note: package.json 5. Open the index.js file in the bin folder. And put the following code in it: .log( ); #! /usr/bin/env node console "Hello World!" The first line starting with is called a line or a line. A shebang line is used to specify the absolute path to the interpreter that will run the below code. The shebang line used here is for Linux or UNIX type systems but node requires it for Windows and macOS too, for proper installation and execution of the script. #! shebang bang Now let’s install and test our CLI. People may call our CLI from anywhere in the system so let's install it globally. 6. Navigate to the root directory of the project and then run ~$npm install -g . The flag tells npm to install the package globally on the system. -g Test the CLI by typing the specified keyword in the terminal. ~$tran If everything was done correctly then you should be greeted with the message which we console.logged in the file. index.js Something like this: All good! Handling Command Line arguments Our basic CLI is ready and now we move to adding further functionality. The most basic task that any CLI does is . In our CLI, we will be receiving the language name and the sentence to be translated as arguments and then we will parse it. handling command-line arguments Although Node.js offers built-in functionality for handling command line arguments, we are going to use an npm package called 🏴‍☠ which is specifically made for building CLIs. yargs will simplify our process of parsing arguments and help us organize command line flags. yargs 1. Install yargs ~$npm i yargs 2. After installing it, include the module in your : index.js yargs = ( ); const require "yargs" 3. Then create the object containing all your command line flags: options usage = ; options = yargs
      .usage(usage)
      .option( , { : , : , : , : })
      .help( )
      .argv; const "\nUsage: tran <lang_name> sentence to be translated" const "l" alias "languages" describe "List all supported languages." type "boolean" demandOption false true In the above code, I have defined an option which, when passed will print all the supported languages by the API, we will implement this later. Yargs provides us with and flags by default. -l --help --version If you want an option to be compulsory then you can set it’s value to , this will get yargs to throw a error if the flag is not provided. demandOption true Missing argument Testing it: Nice! All the arguments that you pass with the command gets stored under the list unless the argument begins with a — or a in that case it is treated as a flag with a default value of boolean. You can console.log yargs.argv to get a better picture about how the arguments are stored. yargs.argv._ -- Access the value of the passed flags using . yargs.argv.flagname Adding Utility Functions Now it’s time to add utility functions. I plan to take input as: ~$tran lang_name the sentence to be translated So we will need to parse the arguments. We can write all the utility functions in our but that wouldn’t look neat so I will make a separate file for all functions. Here’s what we need to do: index.js utils.js Create another file called in the bin folder. utils.js Include the file in your : index.js utils = ( ) const require './utils.js' 3. Create a function for parsing the sentence: Write the function in and then export it: utils.js .exports = { : parseSentence }; { sentence = ; ( i = ; i < words.length; i++) {
 sentence = sentence + words[i] + ;
    } module parseSentence ( ) function parseSentence words var "" for var 1 " " Call it in : index.js sentence = utils.parseSentence(yargs.argv._); var 4. Create a function to show help when no argument is passed: Create a function in your : utils.js .exports = { : showHelp, : parseSentence }; usage = ; { .log(usage); .log( ) .log( + + + ) .log( + + + + ) .log( + + + )
} module showHelp parseSentence const "\nUsage: tran <lang_name> sentence to be translated" ( ) function showHelp console console '\nOptions:\r' console '\t--version\t      ' 'Show version number.' '\t\t' '[boolean]\r' console '    -l, --languages\t' '      ' 'List all languages.' '\t\t' '[boolean]\r' console '\t--help\t\t      ' 'Show help.' '\t\t\t' '[boolean]\n' Call it in : index.js (yargs.argv._[ ] == ){
    utils.showHelp(); ;
} if 0 null return 5. Write a function in to show all supported languages: utils.js .exports = { : showAll, : showHelp, : parseSentence}; { .log(chalk.magenta.bold( )) ( [key, value] languages) { .log(key + + value + )
    }
} languages = ();
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , ) 
languages.set( , ) 
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , ) languages.set( , ) languages.set( , )
languages.set( , ) languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , ) languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , )
languages.set( , ) module showAll showHelp parseSentence ( ) function showAll console "\nLanguage Name\t\tISO-639-1 Code\n" for let of console "\t\t" "\n" let new Map 'afrikaans' 'af' 'albanian' 'sq' 'amharic' 'am' 'arabic' 'ar' 'armenian' 'hy' 'azerbaijani' 'az' 'basque' 'eu' 'belarusian' 'be' 'bengali' 'bn' 'bosnian' 'bs' 'bulgarian' 'bg' 'catalan' 'ca' 'cebuano' 'ceb' 'chinese' 'zh' 'corsican' 'co' 'croatian' 'hr' 'czech' 'cs' 'danish' 'da' 'dutch' 'nl' 'english' 'en' 'esperanto' 'eo' 'estonian' 'et' 'finnish' 'fi' 'french' 'fr' 'frisian' 'fy' 'galician' 'gl' 'georgian' 'ka' 'german' 'de' 'greek' 'el' 'gujarati' 'gu' 'haitian creole' 'ht' 'hausa' 'ha' 'hawaiian' 'haw' // (iso-639-2) 'hebrew' 'he' //or iw 'hindi' 'hi' 'hmong' 'hmn' //(iso-639-2) 'hungarian' 'hu' 'icelandic' 'is' 'igbo' 'ig' 'indonesian' 'id' 'irish' 'ga' 'italian' 'it' 'japanese' 'ja' 'javanese' 'jv' 'kannada' 'kn' 'kazakh' 'kk' 'khmer' 'km' 'kinyarwanda' 'rw' 'korean' 'ko' 'kurdish' 'ku' 'kyrgyz' 'ky' 'lao' 'lo' 'latin' 'la' 'latvian' 'lv' 'lithuanian' 'lt' 'luxembourgish' 'lb' 'macedonian' 'mk' 'malagasy' 'mg' 'malay' 'ms' 'malayalam' 'ml' 'maltese' 'mt' 'maori' 'mi' 'marathi' 'mr' 'mongolian' 'mn' 'burmese' 'my' 'nepali' 'ne' 'norwegian' 'no' 'nyanja' 'ny' 'odia' 'or' 'pashto' 'ps' 'persian' 'fa' 'polish' 'pl' 'portuguese' 'pt' 'punjabi' 'pa' 'romanian' 'ro' 'russian' 'ru' 'samoan' 'sm' 'scots' 'gd' //gd gaelic 'serbian' 'sr' 'sesotho' 'st' 'shona' 'sn' 'sindhi' 'sd' 'sinhalese' 'si' 'slovak' 'sk' 'slovenian' 'sl' 'somali' 'so' 'spanish' 'es' 'sundanese' 'su' 'swahili' 'sw' 'swedish' 'sv' 'tagalog' 'tl' 'tajik' 'tg' 'tamil' 'ta' 'tatar' 'tt' 'telugu' 'te' 'thai' 'th' 'turkish' 'tr' 'turkmen' 'tk' 'ukrainian' 'uk' 'urdu' 'ur' 'uyghur' 'ug' 'uzbek' 'uz' 'vietnamese' 'vi' 'welsh' 'cy' 'xhosa' 'xh' 'yiddish' 'yi' 'yoruba' 'yo' 'zulu' 'zu' Here I have created a to map all the language names to their code. This will , firstly it will help display all languages when needed, secondly, the API only takes the language code so even if the user enters the language name we can swap it with the language code before passing it to the API. Sneaky! 🤫. The swap would be in since we are using a hash map. hash map ISO-639–1 serve two purposes constant time Call the function in your if the or flag is true: showAll() index.js -l --languages (yargs.argv.l == || yargs.argv.languages == ){
    utils.showAll(); ;
} if true true return 6. Now write the function to do the dirty deed we talked about in your : utils.js .exports = { : parseLanguage, : showAll, : showHelp, : parseSentence }; { (language.length == ){ language;
    } (languages.has(language)){ languages.get(language)
    } { .error( ) ; }
}; module parseLanguage showAll showHelp parseSentence ( ) function parseLanguage language if 2 return if return else console "Language not supported!" return //returning null if the language is unsupported. Convert the language to lower case and then call the function in : index.js (yargs.argv._[ ]) language = yargs.argv._[ ].toLowerCase(); language = utils.parseLanguage(language); if 0 var 0 // stores the language. //parsing the language specified to the ISO-639-1 code. 7. Now check if the sentence is empty, if not send it to the API: Include the API at the top of your : index.js translate = ( ); (sentence == ){ .error( ) .log( ) ;
}
translate(sentence, { : language}).then( { .log( + + res.text + + ;
}).catch( { .error(err);
 }); const require '@vitalets/google-translate-api' if "" console "\nThe entered sentence is like John Cena, I can't see it!\n" console "Enter tran --help to get started.\n" return to => res console "\n" "\n" "\n" "\n" => err console Your CLI is complete now! One thing more that you can do is to decorate the output and errors with boxes and colors, we can do that using and . boxen chalk Beautification using Boxen and Chalk We can use terminal colors using and boxes to decorate our output using . chalk boxen 1. Install chalk and boxen. npm install chalk boxen 2. Include them in your and index.js utils.js chalk = ( ); boxen = ( ); const require 'chalk' const require 'boxen' 3. Add color to the usage constant. usage = chalk.hex( )( ); const '#83aaff' "\nUsage: tran <lang_name> sentence to be translated" 4. Display the output using a beautiful box. translate(sentence, { : language}).then( { .log( + boxen(chalk.green( + res.text + ), { : , : , : }) + );
}).catch( { .error(err);
 }); to => res console "\n" "\n" "\n" padding 1 borderColor 'green' dimBorder true "\n" => err console Feel free to explore both the packages and add customization to your heart’s content. :) The CLI in all its glory: Ahh yes Hope you had fun learning how to build your own and fully portable CLI :) because I had a lot of fun. Happy coding! The complete code for this can be found at: https://github.com/RushanKhan1/termTranslate Fork me on maybe :) Github Connect with me on . LinkedIn Also published at https://dev.to/rushankhan1/build-a-cli-with-node-js-4jbi

Stories, News & Mentions about MAGENTASRL

Magentasrl’s Stories on HackerNoon

Magentasrl's News & Mentions