I moved my app to another Ubuntu computer. As soon as I launch the app with meteor or meteor run on the new computer, it errors out with:
EISDIR: illegal operation on a directory, unlink
'/home/hoosiercoder/dev/simple-todos/.meteor/local/dev_bundle'
I checked that directory, I do have symbolic links to an old version of meteor from my old computer. I think that's what generates the error.
The problem is that when I remove all the symbolic links, and try to run the app again, meteor just creates another symbolic link.. again to the old version of meteor. :(
How do I work around this problem and get the app running?
I created a new meteor test app on the new machine
Reinstalled all the libraries
Replaced the .meteor folder in the original app with the new .meteor folder from the test app
This solved the problem on the new box.
Related
I have downloaded angular 2 application from this link:
https://github.com/aravindfz/firstAngular2App
How to run this application?
Which angular cli version install to run angular 2 application?
I tried from some questions stackoverflow but not working properly.guys this question is not duplicate..Please understand.
Anyone can give clear details?
I need step by step procedure.
If you cloned the repo and did nothing else, there are a few things you need to do before you can run the app. Since I don't know how much web development you have done, I'm going to include things some people will think unnecessary.
Install node.js, if you haven't yet. Grab the LTS release from https://nodejs.org/en/. Do not use the "Current" version, because that may not be compatible with Angular just yet. If you have and older version of Node, upgrade. If you already have the LTS version, skip this step.
Now open a new command prompt or terminal and change to the directory where you cloned the repo. To be sure you're in the right place, make sure you can see a file named package.json.
In this command prompt/terminal window, execute this command: npm install. This will download and install all the dependencies (which could rather disturbingly add up to a few hundred Megabytes). You may experience timeout errors if you're behind a corporate proxy server. That's not something you can fix as of 2018. Just connect using something else and try again.
Once everything is installed, you should be able to run the Angular app. Everything I mentioned already only need to be done before you run it the first time. To ensure you are in the right folder, navigate to where your index.html is located and run this command: ng serve. If ng cannot be found, you may need to install it. To do so, execute npm install --save-dev #angular/cli. Now it should work. If not, close your command prompt/terminal window, open a new one and try ng serve again.
Once ng serve is finished compiling, you should be able to view your app by opening http://localhost:4200 in your favourite browser.
And that's it!
Here's a bonus tip: Take the time to work through the official Angular Quick Start. It really is a fantastic guide and will get you skilled up much quicker than just hacking it ever will.
Good luck.
I have recently experienced a serious problem with Rstudio when developing a package. Whenever, I open an existing project with Rstudio where versions are controlled with Git, it takes so long for it to respond to any command. It is also impossible to type something in the console (e.g. 1+1) and obtain the result. Even quitting the Rstudio, should be done with task manager. There is no problem when I create a new project / package or when I open directly a R script.
This problem appears both when the project is saved on a dropbox or on a local repository.
To overcome this issue everytime I need to modify my code, I create a new project, and then I move toward the new repository all my current R scripts and the folder ".git".
I would appreciate if anybody could help me with this issue.
I had a similar problem to yours. Changing the attribute of my .git folder into hidden solved my problem.
We recently discovered an issue where projects using git for version control could become laggy / unusable on Windows if the .git folder within the project had become a non-hidden directory.
https://github.com/rstudio/rstudio/issues/1918
I'm working through the Angular2-Meteor tutorial here. When I update the code for the app, I frequently encounter an error message, displayed in the browser console when I browse to the app running on localhost:
Error: There can be only one platform. Destroy the previous one to create a new one.
Sometimes the app seems to be running fine. Other times it is indeed not working. What does this error mean, and how should I fix it?
This happened to me when i was using the Atom editor. Atom compiles your typescript and outputs it in the same folder by default. Then Meteor sees both a *.ts and a *.js file and happily loads both of them. As a result 2 Angular platforms are created.
I don't know if you can change the *.js output folder with atom-typescript. I switched to VSCode for typescript development.
I'm on a 64x Windows 7 machine, and just downloaded the new Windows Meteor platform. I have no trouble creating a "Meteor" file within Windows32, but when I then use the "meteor create experiment" command to create meteor specific files within my "Meteor" file, it creates the new file on SysWOW64, instead. If I try to change directory from within the System32 file, I get a "This system cannot find the path specified" message. No problem if I cd to "C:\Windows\SysWOW64\Meteor\experiment".
I can't imagine meteor 1.1 is 32 bit, so how can I stop the computer from redirecting the file creation process?
As a warning, I am truly a newbie to programming. Please don't tell me to do things without also making clear what I'll need to learn to be able to do it.
Thanks!
The default meteor installer appears to be 32 bit (You can verify this by running meteor --arch in the command line, which should print os.windows.x86_32). This is the reason why the new file is created in SysWOW64 instead.
It's also not really a good idea to create projects inside of System32 to begin with, as it is reserved for windows system files.
I am having trouble with my Meteor up, which is perfectly functional on localhost and on Modulus. When I try to deploy to a *.meteor.com instance the upload fails and I get a very cryptic error. The first line is the gist of it I guess
Error: not a tracked temp dir: /Users/valentin/.meteor/packages/velocity_core/.0.4.5.1dbi101++os.osx.x86_64+web.browser+web.cordova
I have tried installing and reinstalling velocity and tried deploying it with/without, the error persists. There are a bunch of hidden files in the folder the error points too. Deleting the one mention in the error simply creates new ones and throws an error again (naming a different folder though) Does anyone have an idea what it is about?
I had the same problem with another meteor package. It was solved after I delete everything from myapp/.meteor/local/ directory.
I think you can leave your local db there (myapp/.meteor/local/db), but I did not check if it still be working. (I've deleted all and probably it is the same as running meteor reset for your local project.)
OK, this seems to work: You have to manually downgrade the meteor version to 1.0.2.1, by editing .meteor/release and changing the version number. (There's a fix in dev, so it should be solved in a more complete fashion soon.)
Were you trying to deploy while your meteor app still ran in localhost? I faced the same problem for another package but resolved it by stopping my local meteor app first then deploy.