I trying to acquire this plugins which available with its GitHub directory
https://github.com/jbeuckm/strapi-plugin-import-content
However, the last command:(not workable)
npm run setup --plugins
It prompt me this:
enter image description here
May I know how could i solve it?
I try "npm cache clean --force" but it still not workable
'npm run setup' was available in Strapi 3.x but as far as I know it is no longer available latest by version 4.x - I guess you are using Strapi 4.x.
https://github.com/jbeuckm/strapi-plugin-import-content was updated 4 years ago so I think it was designed for Strapi 3.x.
Related
Hi I'm a little stuck with with this. Never had this issue in the past. I get this error below in capistrano log details. I tried to update mimemagic and followed this here https://www.rubydoc.info/github/mimemagicrb/mimemagic
The error
Your bundle is locked to mimemagic (0.3.5), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of mimemagic (0.3.5) has removed it. You'll need to update your bundle to a version other than mimemagic (0.3.5) that hasn't been removed in order to install.
I appreciate your help with this.
So this is due to mimemagic being yanked due to copyright issues. Anyways, I'm on a mac and I'm using rails 6, I'm not sure what you'd do if you're using older versions of rails. My issue got solved by doing the following:
First please make sure you have work committed to git prior to doing anything.
In gem file
gem 'mimemagic', '>= 0.3.8'
Then in your terminal run
brew install shared-mime-info
or you may have to run
brew upgrade shared-mime-info
Finally run
bundle update marcel mimemagic
So that solved the issues for me. Here is a good reference.
https://github.com/mimemagicrb/mimemagic/issues/98
Also you may want to follow up on any copyright infringements.
We have a CD/CI Azure DevOps build pipeline that stop working all of a sudden today. It has been invoked successfully in our pipeline for months on end.
The component that fails is the "npm install" , it fails with the following error in the verbose log:
I google around and some suggested to run: npm cache clear --force prior to npm install.
I tried that but same error persists.
Then I look up earlier in the log and see the following:
I tried to browse to https://github.com/sass/node-sass/releases/download/v4.12.0/win32-x64-83_binding.node and got the message "Page not found".
I cannot tell if this is related to the root cause why npm fails but it seems to back my assumption that something is not right with "npm install" as of this time of writing (Nov 17, 2020).
Anyone else using Azure DevOps for CD/CI having the same issue?
I look at NPM incident page and see this issue https://status.npmjs.org/incidents/r1tlhscrw3r6 but it should have been fixed.
Recently, a breaking change was made to the default Azure DevOps agent images for the default version of Node.js. It was incremented from 12.x to 14.x.
Breaking changes
Default version of Node.JS on images will be updated
from 12.x to 14.x
Target date
For Windows, Ubuntu images, rollout of this change will
start on 2 November 2020 and will take 3-4 days For MacOS images,
rollout will start on 9 November.
The motivation for the changes
On images, we always install LTS
version of Node.JS by default. On 2020-10-27, Node.JS 14 has become
LTS version. On 2020-11-30, Node.JS 12 will be switched to Maintenance
mode.
Possible impact
If you rely on default Node.JS version and your
project is not compatible to Node.JS 14, it might start to fail
Mitigation ways
Please consider using Node.js Tool Installer task (for Azure DevOps) and
setup-node (for GitHub Actions) to switch back to Node.JS 12.
Switching will take less than a second. Node.JS 12 still will be
available on images along with Node.JS 8, 10.
Based on #Matt's answer, I'll post the fragment of yml you need to fix this:
- task: NodeTool#0
inputs:
versionSpec: '12.x'
For anyone still using the graphical UI rather than YML files, you would add a
"Node.js tool installer" task and configure its version. It would look something like this (where the Version Spec contains the version of node.js you want run):
Also note that it is BEFORE the "npm install" task!!
Issue:
I am currently experiencing issues with getting Ionic set up for Moodle mobile app development.
What have I tried?
I am currently following the Moodle documentation.
However, when I run the command npm run setup I get the warning:
npm WARN tarball tarball data for mathjax#2.7.7 (sha512-OOl0B2/0tSJAtAZarXnQuLDBLgTNRqiI9VqHTQzPsxf4okT2iIpDrvaklK9x2QEMD1sDj4yRn11Ygci41DxMAQ==) seems to be corrupted. Trying one more time.`
It takes really long to extract on the retry.
copy of the issue.
Same problem. Only having this issue on my windows install though. Not a problem on linux.
It freezes on that tarball. To get past it I did the following in moodleapp directory:
npm cache clean --force
npm install mathjax#3
npm run setup
...will see how the rest of the environment setup goes.
It says I have used the pro version so I need the licence or free trial.How can I get the free version of angular cli on eclipse.I have tried to reinstall it but did not work.
As far as I know, Eclipse does not support Angular CLI. Try taking a look at IntelliJ's trial version. (https://www.jetbrains.com/idea/)
You don't need an IDE to use Angular CLI. All you need is a Terminal.
Run the following steps:
You need Nodejs. If you don't have it yet, just go this official
nodejs page & download the recommended version then install it.
$ npm install -g #angular/cli
Angular Eclipse is open source and integrates angular-cli with Terminal, Wizards and Launches.
I am trying to deploy a Java project into Google App Engine from Eclipse and am blocked by JSPs.
Everything JSP makes my app not capable of deploying due to "'utf8' codec can't decode byte" error.
Not trying to insert any strange (not UTF-8) character, everything Eclipse is set to UTF-8.
Tried to send archives which were OK with the Google App Engine Tools for Eclipse (soon to be deprecated), won't deploy.
I've seen threads regarding reverting the Google Cloud Tools for Eclipse plugin to previous version (1.58 seemed to avoid a few problems) being a possible solution to these recent errors but I have a problem installing, the batch just tells me "Install will exit" ?!
Tried to uninstall previous (latest) versions before, made sure I was launching the bundled-python batch, still not capable of installing an old version of the Google Cloud SDK shell.
Would be glad if anybody had any suggestion at what makes my install fail.
Thanks in advance.
There are a few ways you can get older version of Google Cloud SDK.
Download versioned archive
(If you are on windows) Grab google-cloud-sdk-XXX.0.0-windows-x86_64-bundled-python.zip file.
Unzip it to some\dir
Add some\dir\google-cloud-sdk\bin directory to your system path
Restart your command prompt (or other apps which depend on gcloud) and run for example gcloud info, it should be fully functional installation, no need to run install.bat.
Alternatively, use existing SDK installation and gcloud component manager to go back to previous versions. For example
gcloud components update --version 158.0.0
target by version number using apt-get :
sudo apt-get install google-cloud-sdk=294.0.0-0