I'm using Nuxt to create my frontend application in which I would like to add vue-toasted.
However after installing following the documentation :
yarn add vue-toasted
add '#nuxtjs/toast' to modules into the nuxt.config.js file
The server cannot build due to this error :
ERROR Nuxt error
Error: Cannot resolve "#nuxtjs/toast" from "/front/nuxtjs/toast"
I am running nuxt in a docker container but I already installed depencies succesfully such as bootstrap-vue…
I posted my question on nuxt forum but it seems to be completly dead.
Thanks in advance for your help !
Nevermind, it was a silly mistake on my hand, it was the package #nuxtjs/toast that needed to be installed and not vue-toasted -.-
Related
I recently updated my Azerothcore docker version, but I am encountering an error: "azerothcore-wotlk-ac-worldserver-1 | MMAP:loadMap: 5303231.mmtile was built with generator v15, expected v16". I have tried deleting AC and installing from scratch following the guide on the Azerothcore website, but when I run "./acore.sh docker client-data", it is still downloading client data files for v15 instead of the latest version v16. I have followed the Docker Setup and Azerothcore Bash Dashboard setup, but I am still having issues. Does anyone know how I can fix this problem?
Thanks in advance for any help.
Best regards.
This sounds to me like a PR is required to fix the setup process of docker. If a manual swap of the client data isn't sufficient, only an adjustment of the docker script can solve this.
You should create an issue about it in the respective repo you've cloned, azerothcore-wotlk or acore-docker.
Edit: Please update and try again due to https://github.com/azerothcore/azerothcore-wotlk/pull/14527
I am trying to display docs stored in repository created by backstage io component on backstage-io /docs page UI, but when I am trying to access the docs I am getting the following error
Building a newer version of this documentation failed. Error: "Failed to generate docs from C:\\Users\\Admin\\AppData\\Local\\Temp\\backstage-enprxk into C:\\Users\\Admin\\AppData\\Local\\Temp\\techdocs-tmp-W6iVab; caused by Error: Docker container returned a non-zero exit code (1)"
Files in my repository
docs folder only having index.md
and mkdocs.yml have
nav:
Home: index.md
I was getting similar issues working on a local POC of Backstage. The biggest problem was that I needed to install pip, python, mkdocs, and mkdocs-techdocs-core (i.e. pip3 install mkdocs-techdocs-core). If you have done that and then followed everything in this documentation, then it should start working. Hope that helps. I spent a couple of days trying to get past these types of errors.
For me the above issue is fixed by using below as it was not working inside my container in kubernetes.
I changed app-config.yaml -
techdocs:
builder: 'local' # Alternatives - 'external'
generator:
runIn: 'local' // changed from docker to local here
Has anyone run into this before?
I am doing a local install of Drupal 8 with docker and composer. I'm on a Windows machine using WSL. When I clear the cache (drush cr), I get this error:
Service "slick.manager": Parent definition "blazy.manager.base" does not exist.
Both Slick and Blazy modules and libraries are present. When I try to go to the site it says "The website encountered an unexpected error. Please try again later."
Any help would be greatly appreciated.
Just uninstall the slick module, load the site, install blazy, then enable the slick module again. It's an "ordering" issue due to a new dependency.
See; https://www.drupal.org/project/slick/issues/2702241
It's a bit of a workaround but it should solve your problem.
If this isn't the issue, then please update your question with the output of;
drush pml --status=enabled
(Just for the two modules if you don't wish to copy everything here).
I am currently following a GraphQL Tutorial and am on the "Add a Database" section explaining how to set up Prisma with GraphQL.
I finished adding the information in the prisma.yml file, installed prisma, ran prisma deploy and followed the steps, but every time I run prisma info, prisma token, or prisma deploy again, I keep getting the same error:
TypeError: url_1.URL is not a constructor
I have been trying to look up solutions to the error. I tried updating node and npm, downloading docker but nothing seems to be making any difference.
Help would be greatly appreciated.
You are running into this issue.
Basically, this is a known issue with node 6.x.
Please update the node version to fix this issue and track the progress of above issue in case you want to continue to use node 6.x.
I tried to install Neos CMS local under Windows 10 with a Wamp Apache Server. After creating the project with a composer and registering the Vhosts, I tried to run neos.demo/setup. Then I get an 500 internal server error with the message "Specified path not found”, for more information, take a look at the screenshot.
I checked the solutions for the exception code 1355480641, but nothing can solve my problem.
Thanks for your recommendations!
do you have set Neos.Flow.core.phpBinaryPathAndFilename in Configuration/Settings.yaml to the correct php.exe binary path?
This is not an actual solution, this is more of an alternative.
I was having troubles installing neos on windows 10 as well (not the same as you though), a really nice solution that I would recommend as alternative to wamp is bitnami-neos.
I got the same error in the current version of Neos CMS (v4.1). The solution to the problem was for me:
Adjust Configuration/Settings.yaml with the php.exe path (which you already did)
Launch an administrator cmd
Go to the Neos CMS directory
Run flow flow:core:compile
Run flow flow:cache:warmup
Now I could access Neos with XAMPP.
All credit for this answer goes to the following post: https://discuss.neos.io/t/running-neos-flow-on-windows-10-success/2752