I am working with ionic 2. And I don't know why when I'm trying to run 'ionic serve', it answer with the next messeges:
WARN: ionic.config.js has been deprecated, you can remove it.
WARN: No 'serve:before' gulp task found!
Your gulpfile contains a 'watch' task already! Add:
gulp.task('serve:before', ['watch']);
to your gulpfile to have Ionic CLI run 'watch' before serve.
WARN: ionic.config.js has been deprecated, you can remove it.
In the gulpfile.js I add that line and it works, but when I change some html file it don't update. I have to stop serve. And run the command again.
PD: I have alredy install all dependencies with npm install
Thanks
Recently Ionic updated their CLI tool (to beta.21). They have obviously made some changes in the gulp file which is being generated by their newly updated CLI. The project you are trying to run was created using an older version of CLI (probably beta.19). That's why you are getting that warning. Regarding the 'ionic.config.js has been deprecated' line, that file is simply a checkpoint to see whether you are using the latest version of Ionic CLI.
There is a quick fix (which I did).
1) Create a new ionic app (possibly using the same template as the one you are trying to run i.e., blank or sidemenu or tabs).
2) Copy the contents of the app directory of the project which you are trying to run to the app directory of the newly generated project.
(I don't know whether this is the right method, but this will work.)
Hope this helps you. Thanks.
Related
I created a fresh vue project with the new version which includes vite init.
When I run npm run build a dist/ is created. But when I open dist/index.html inside the dist folder it doesn't show anything. My question is how can I build the app and run it without any command (Building for production). Thanks
You need a server, otherwise assets will fail to be found and you'll get errors and a blank page. Use npm run preview.
I've got NativeScript 3.3.0 installed. My project-wide CSS is in app/app.css.
When I run the app, either by console
tns run android --device [device-ID of my preferred emulator]
or by starting it in an Android emulator through JetBrain's WebStorm (with NativeScript plugin installed), the app.css always gets minified during the rebuilding process after I do some changes to it while the app is running.
Is it somehow possibile to prevent NativeScript from minifying the CSS file upon building the app? I wished there was a run parameter with which I could toggle that.
Looks like you have nativescript-dev-sass installed
if you uninstall it, the minification should stop.
But ideally, you would want to keep the minification.
Edit:
you can do,
npm remove -D nativescript-dev-sass
and you remove those nativescript-dev-sass files which are in hooks folder (if it doesn't get removed automatically).
Also if you see node-sass in your devDependencies, remove that as well with
npm remove -D node-sass and you should be good to go. Cheers!
I'm trying to create a run configuration in IntelliJ that will build my projects and run both ng serve (Angular CLI) and WebLogic Server simultaneously. I have installed the Multirun plugin in IntelliJ that allows multiple run configurations. I was able to create a run configuration for WebLogic Server however I cannot figure out a way to create a configuration that simply runs Angular CLI since it is ran through a command line.
Is there a plugin that I could use to initiate Angular CLI in intelliJ?
I ended up finding a solution to this issue. The only way that I could think of for running Angular CLI through a Run Configuration was to create a .cmd that opens up command prompt and starts the server. I stored this .cmd file within the project that needed Angular CLI and made that file my startup script in the WebLogic configuration. The same has to be done for the "Run" startup script and the "Debug" startup script.
When run (green arrow) is clicked, WebLogic runs inside of IntelliJ and a separate command prompt window opens and runs the Angular CLI.
I am working on an existing project of Angular 2. I added few modules on that project and on the files I added changes are not being detected.
I tried googling how these detect changes work in angular 2 but didn't get the right answer. Can anyone help me direct in which settings/files should I be looking into if I have to enable detect change and compile my new modules in Angular 2.
If you are running the angular cli you can run the command ng serve to detect changes and run your application at localhost:4200. Or you can run the command ng build --watch to observe changes. You will need to manually refresh the browser each time this recompiles.
I am trying to get up and running with Meteor and seeing what it can offer, while I like it overall, it seems it's a very very rigid system.
I set up a small testing setup using Velocity, it opens a small overlay window on the side which has a class of "velocityOverlay". The overlay is really small and makes error stack traces wrap. All I wanted to do was to edit the css of the "velocityOverlay" and increase the width.
I somehow (after wasting time) managed to find that Meteor is actually putting all the packages in my user directory by default, once I found that, I found the needed css file...
velocity_html-reporter/.0.5.1.aykpxq++os+web.browser+web.cordova/web.browser/packages/velocity_html-reporter/lib/client-report.less.css
And I did a small edit to the width, next thing you know the meteor app crashes when trying to launch using the "meteor" command throwing a "Error: couldn't read entire resource" error. I can't even edit the bootstrap.css file I installed using "ian_bootstrap-3".
Further more, I can't find any way to install packages locally just for my particular project, what if I wanted to modify a package only for my particular project? this is very easy to do in vanilla Node.js, you simply don't use the "-g" when using "npm install".
To add to that, within my project root, there is another ".meteor/local/build/web.browser" folder with most of the global package files replicated again. When does Meteor use which? This is very confusing.
You can run a package locally very easily.
Download it from Github (for example) and put it in the packages/ directory of your application like this /packages/package_name.
Then add it to your application with the same meteor add package_name command as usual.
Meteor will automatically look in the local folder before anywhere else and compile the package with the rest of your code.
This allows you to do any modification you want on the package and test it locally before publishing it to the registry.
Also, folders located in .meteor/local/* are used for building purpose only and are generated automatically by Meteor. So it is not the best place to edit the files!
This worked for me https://atmospherejs.com/i/publishing. mrt link-package didn't work for me, might just be outdated code.
Steps:
Download (or clone) package from GitHub to local dir
Stop meteor if running
2.1. Make sure you have a packages folder: mkdir packages
Locally link your package:
3.1 If you have mrt installed: Run mrt link-package /path/to/package in a project dir
3.2 If you don't have mrt: ln -s /path/to/package packages/package
Then run meteor add developer:package-name, do not forget to change package name
Run meteor in a project dir
From now any changes in developer:package-name package folder will cause rebuilding of project app
Download the package and place it in new package directory in your project root.
open the package.js inside the downloaded package and remove the author's name in the property "name:"
e.g: - name:'dburles:google-maps' to name:'google-maps'
then run
meteor add google-maps