cli-app | sample command line application used in the JSReadme blog | Runtime Evironment library

I think you'll struggle without arguments tbh; most apps I can think of that have this dual mode operation bundle as two exes, a gui one and a command line one (and one maybe uses the other)

It really is the simplest way to just have rules:

• if the application is started with no arguments, print(and/or messagebox.show) the command line arguments and quit
• if the app is started with eg /gui argument (baked into the windows shortcut) it runs as gui
• if the app is started with other arguments for command line operation, proceed as per those arguments

You can vary these of course, maybe you would have:

• if the application is started with no arguments, run as gui
• if the app is started with eg /? argument print the command line arguments and quit
• if the app is started with other arguments for command line operation, proceed as per those arguments

I make this recommendation chiefly because, to be really useful as a command line app an app probably needs to take arguments from the command line, so you can use their presence or absence to infer where the app was started from. It's not perfect, of course - a shortcut can "start from windows" but pass arguments that will make i the app think it was command line, but where I'm getting to is that generally that doesn't matter because this question is not so much about "where it was started from?" as "does the app have enough info to do its work or must it ask the user for info?"

Please ensure that "@glimmer/component": "^1.0.0" line exists in your package.json. Then rerun npm install or yarn install and restart ember s. This should be there if you had used ember new with Ember 3.14+, but it seems like it might be missing.

You just need to change line "typescript": "^3.7.2" -> "typescript": "~3.7.2"

Somehow your typescript got updated to 3.8, which has this issue: https://github.com/typed-ember/ember-cli-typescript/issues/1103

You can do it without changing any node_modules files by using @angular-builders/custom-webpack to setup custom Webpack rules and as you mention node-sass-json-importer to import JSON files inside SCSS files.

You'll have to install node-sass for the implementation option because node-sass-json-importer is compatible with node-sass.

1. Install packages @angular-builders/custom-webpack, node-sass-json-importer and node-sass:

Yarn tells you that the npm package find-up is expecting a Node version greater or equal 8. Accordingly to your question you are using Node 6.

End of life for node 6 was on 30 April 2019. Even Node 8 not supported anymore since end of last year.

You should upgrade to a supported version of Node to resolve that issue. Node 10 and 12 are active LTS versions. Node 13 is the current latest release. You could find an overview of Node versions and their support at https://github.com/nodejs/Release.

The best way for me is:

• Create a project with ng new
• Install bootstrap, jquery and font-awesome with npm install bootstrap@4.0.0-alpha.6 jquery font-awesome

• in your .angular-cli.jsonadd:

  "apps": [{ "styles": [ "styles.css", "../node_modules/bootstrap/dist/css/bootstrap.min.css", "../node_modules/font-awesome/css/font-awesome.min.css" ], "scripts": [ "../node_modules/jquery/dist/jquery.min.js", "../node_modules/bootstrap/dist/js/bootstrap.min.js" ]

This will automatically compile the bootstrap css and javascript, font-awesome and jquery, which is required by the bootstrap js, in your index.html.

Note: The jquery.min.js under scripts must be included before the bootstrap.min.js is included, because bootstrap.min.js requires jquery.min.js to work properly.

UPDATE: Bootstrap 4 requires tether.js. Install it with npm install tetherand add it to your scripts in .angular-cli.jsonBEFORE bootstrap.min.js.

If I understand what you're asking, this can be handled in the setup.py as you say.

Don't use npm. Use yarn. It's faster, more secure and has better cache. It's also recommended as migration path from Bower (by Bower). Yarn is also recommended by Ember team instead of npm.

Ola @Divakar, thanks for your question! And Welcome to Ember

Looking at your question it seems like it could be related to an issue that we had recently in ember-data where the generators were broken. I think they were fixed in ember-data@3.11.1 but from your package.json it would seem that you have ember-data@3.11.0

If you want to update ember-data and see if the issue is still there you can run the following: