I have created a project using vue.js at the frontend and flask at the backend, It was working perfectly. But, after I customized my ubuntu OS, suddenly I am unable to run the project, my flask and every other framework and library was uninstalled and I am unable to reinstall vue and I get this error message when I try to install vue again:
Can someone tell me how to resolve this issue?
By Customization, I installed some extensions and then some wallpapers, icon packs etc..
As a user has mentioned in the replies earlier, what you are trying to do is installing a global package, and the error displayed there clearly stated that you lacked permissions, and the customizations you mentioned should not have any impact on this.
Since you are using Ubuntu, just add a sudo in front of the command that you are trying to execute and it should be fixed.
Related
I've been using the command line for some time now, but I'm still not sure what exactly happens when I do certain things - and I'm not sure what to google for help.
When I'm working with Anaconda and Python, I found the environments I created in C:\Users\<User>\Anaconda3\envs. And every python package I install in an environment seems to go there. Great!
But how does this work outside of Anaconda/Python? For example, I installed the vue CLI via npm install -g #vue/cli. What exactly happens when I do this; or more precicely, where are files saved?
During the creation of a new vue project, a readme.md is created as well. It states that users should simply npm install to setup the project. It seems that this command installs all packages stated in the package.json. I would like to try out if this command works for new users, but I already (obviously) have everything installed. Can I create some kind of environment (like I do with Anaconda for Python) to accomplish this?
Thanks a lot for your answers!
Problem Summary
So I'm trying to launch a new Gridsome project for local development. I've toyed with Gridsome in the past and had a great experience, so I decided to give it another shot.
This time around; however, when I run the gridsome create command, the system creates a new Gridsome site directory as expected but returns the following error message:
The instructions in this error message say to enter the newly-created site directory and run gridsome develop to start local development. However, after running cd my-gridsome-site and subsequently running gridsome develop, I then receive this error:
So far, I've tried running npm install --save from the site directory as well as yarn install, both to no avail. Thinking that this was possibly tied to my terminal, I switched from using the Zsh terminal to using the Bash terminal. This also did not work.
I'm at a loss here and could really use a hand.
Thank you for helping,
David
This seems to be an environment error. Gridsome requires Node.js (v8.3+) and recommends Yarn.
Make sure your Node.js version is v8.3+ and use only one package manager like Yarn.
to check node version: node -v
I had this same issue, but I resolved it after installing yarn and running the project with yarn instead of NPM. So you should try using yarn it will help,
I am using version 4.5.5 of jhipster.
My OS is Linux Mint.
I am using IntelliJ as my IDE.
Everything is working fine in terms of generating the code, building and running the code.
Client
Unfortunately, when I make changes to the client code (html or ts), the changes are not reflected until I recompile the client code completed. To achieve this I do "mvn -Pdev,webpack". It takes quite a while to restart the client and this is really holding me back.
Hot Deploy
What I expect to happen is that I can run "npm start" and when I save a change to a ts or a html file that it will be picked up and the change immediately visible in the browser.
Questions
Any ideas why the client hot deploy is not working ?
Any ideas how I identify where the issue is ?
For example, how do I know what folders are being watched by the hot deploy ?
Thanks a million for you help.
I am sure others have encountered the same issue and will read the answer gladly.
Kind regards,
Fergal.
PS Need any details, simply ask.
Figured it out.
Somebody else had a similar issue with a globally installed instance of webpack.
I installed a local version and the file updates are being detected and recompiled and the app hot deployed. Now working perfectly.
To install a local version webpack.js.org/guides/installation/#local-installation.
I'm stumped. I cannot understand the getbootstrap.com Getting Started info. I'm running on Windows 7 Pro. I would like to use Pingendo - which I'm new to - to create my website.
I downloaded the distribution version bootstrap-3.3.7-dist.zip (pre-compiled) and unzipped it. Then I came to the MaxCDN code. Where do I put that code??
For the source code version, I see references to things I don't know about: Bower, npm, Composer, Grunt, Less, and SASS. All these appear to be Linux based tools - from the command lines shown. How does one accomplish the same thing under Windows without installing yet more tools? Do I even need to compile this code to use the greater features?
You can either add the downloaded bootstrap css and js files to your project and reference them or you can just use the cdn which is just the same files hosted on a server. You do now have to know about any of those to get started with Bootstrap. They are just additional ways to install it, and different preprocessors that you can leverage.
Im doing some dev work on a dnn module. I was able to build and install a package on my installation of DNN once. I made some changes and wanted to uninstall and reinstall it. Uninstalling went fine. Installing the module again failed by throwing a 404 on the install popup window as soon as i upload the new module zip. I dont see anything logged in the event viewer. Anyone know what can cause this?
Im running DNN 6.2.4
UPDATE: adding more info
the url its 404ing on is: "/Host/Extensions/tabid/36/ctl/Install/rtab/36/portalid/0/Default.aspx?popUp=true"
Im sure this is something unique to my module. I tried installing other modules and they worked fine.
Try hitting F12 in your browser to load the Developer console and see if you can find what the URL is that is 404'ng, that'll make tracking down the issue easier.
Update: Since it appears to be the old "max upload size" issue check out this video for how to fix that part
http://www.dotnetnuke.com/Resources/Video-Library/Viewer/Video/383/View/Details/How-to-increase-the-maximum-file-upload-size-in-DotNetNuke-6.aspx