Yarn start не работает

Ошибка: запуск пряжи — ошибка Команда «запуск» не найдена

Я пытаюсь изучить React и использую частное репо, чтобы начать с него.

Я запускаю yarn start в каталоге репозитория, но получаю сообщение об ошибке:

У меня есть узел и пряжа.

Я попытался переустановить узел и пряжу, но получаю одно и то же сообщение об ошибке. более того, я попытался удалить шанс пряжи через yarn cache clean , но ничего не помогло.

package.json содержит следующее:

Каталог организован следующим образом:

9 ответов

В сценариях файла package.json нет команды start .

Может быть, вы хотите вместо этого выполнить команду test — npm test / yarn test ?

Решил это благодаря проницательности пользователя: Цветан Ганев.

Я пытался выполнить команду, которой нет в моих скриптах. В частности, yarn start отсутствует в scripts части файла package.json . Чтобы решить эту проблему, я добавил следующую строку в scripts

Добавление этого в package.json сработало для меня

У меня была похожая проблема, когда в моем package.json есть скрипт «start» . В конце концов я понял, что не сохранил package.json , поэтому получил эту ошибку. Очевидно, после сохранения package.json проблема была решена.

Проверьте файл package.json, в котором есть сценарии запуска. если у вас просто есть список зависимостей, убедитесь, что у вас есть следующее в package.jons

В противном случае запустите это в папке, где находится package.json

Ошибка команды «Пуск» не найдена.

Theia должен начать на порту 8080 минимально.

Если вы используете create-реакции-приложение и столкнулись с этой ошибкой, скорее всего, вы не установили приложение-реагировать-успешно.

Попробуйте удалить глобально установленное create-create-app, как описано ниже.

Эта проблема возникает, когда файл «package.json» будет удален или изменен. Пожалуйста, проверьте ваш файл «package.json».

Вы также можете попробовать запустить сначала npm install и npm run или yarn start

Источник

Yarn start does not start the Server (but NPM does) #505

Comments

kedoska commented Feb 9, 2018

After creating the project, the output in console (probably from create-react-app ) is this one

yarn start is not starting the web server.
npm start works just fine.

The text was updated successfully, but these errors were encountered:

jaredpalmer commented Feb 9, 2018

Weird. Will have to try this out.

corydeppen commented Feb 11, 2018

Could this be related to #292? I’m seeing this happen on Win10 using Yarn, where it runs fine on the second attempt.

kedoska commented Feb 13, 2018

Small update,
today i created another project from scratch.

the first yarn start did not reached the Server-side HMR Enabled!
the second intent went OK

So apparently it is not related with yarn

marcellobarile commented Feb 16, 2018 •

I’m experiencing the same issue and I’m not using yarn (the same behavior appears on Windows and GNU/Linux). sometimes the process just got stuck on «Your application is running at http://localhost:3000» (no other outputs) even though the server is never started.

josesuarezcordova commented Jul 27, 2018

I have the same issue on Mac

I got apparently everything fine

Sorry , I get the same error after run

seems like everything fine

the browser open but never load the web, my project is under bedrock the structure of web folder is

I ran already yarn install on root folder and theme folder too

stale bot commented Sep 25, 2018

Hola! So here’s the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally—seriously—this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal.

stale bot commented Oct 2, 2018

ProBot automatically closed this due to inactivity. Holler if this is a mistake, and we’ll re-open it.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

yarn start fails with error message #1155

Comments

mocheng commented Dec 5, 2016

Description

yarn start fails with below message

yarn start v0.15.1
$ «react-scripts start»
sh: react-scripts start: command not found
error Command failed with exit code 127.
info Visit http://yarnpkg.com/en/docs/cli/start for documentation about this command.

Expected behavior

According to the prompt after creating a project, yarn star should work.

We suggest that you begin by typing:
cd xyz
yarn start
Happy hacking!

Actual behavior

Tell us what actually happens.

Environment

Operating system: MacOSX 10.12.1

Reproducible Demo

1. Globally install create-react-app and create one project called xyz .
2. Follow the prompt instructions;
3. yarn start fails, but npm start works.

The text was updated successfully, but these errors were encountered:

gaearon commented Dec 5, 2016

I can’t reproduce with Yarn 0.17.6.
Can you please run yarn self-update and try again?

dchambers commented Dec 5, 2016

Hey @gaearon, I just ran into the same problem. For me, yarn self-update didn’ work (as explained here), but I was able to get past that by using npm -g install yarn instead, and it worked as expected after that.

mocheng commented Dec 6, 2016

After upgrading yarn to 0.17.10, it turns to be working.

zverbatim commented Jun 28, 2017

worked for me after running just the command yarn in project folder

zawmoelwin commented Jul 24, 2017

It works. Thanks @zverbatim .
For me, accidental npm install —save the package induced the error.

the solution is ..
reset the git
yarn
then yarn add packageName solved the error.

n1c01a5 commented Aug 29, 2017

peggyc3 commented Oct 24, 2017

I had a similar problem, caused by installing a package using npm instead of yarn, which is what I was using for this project. I got the react script not found error message and the server would not start. To fix it, I ran yarn, then ran yarn start and the server restarted. SUCCESS 🙂

y0n1 commented Dec 22, 2017

Well, I know I’m joining the party a bit late. but this was my setup:

• macOS (High Sierra)
• I’m using NVM
• I’ve installed Yarn using Brew

So, when I stumbled upon this issue the only thing which helped me was:

1. brew uninstall yarn
2. rm $(which yarn)
3. rm -rf

Hope this helps somebody too

dapperAuteur commented Dec 28, 2017 •

having the same issue, yarn self-update didn’t work for me. I ran yarn -v and it printed my version then updated. I was on 0.24.6. It works now.

Arpanbhalla commented Jan 9, 2018

ghost commented Feb 28, 2018 •

I experiences the yarn start error on 4 different laptops running Ubuntu and resolved it using these steps.
The underlying issue was that the yarn path was set incorrectly.
If you have this error then you will see a yarn-error.log file in you project directory rather then a normal yarn.log file.
But if you reinstall Yarn on Ubuntu, it will also CORRECT Your React * path to yarn and this error.

— After you did these STEPS, Go To Your Project and BUILD & START Your Yarn:
1. yarn bulid
2. yarn start

Источник

Error: yarn start — error Command «start» not found

I am trying to learn React and I am using a private repo to start with it.

I run yarn start in the directory of the repo but I get the error message:

I have both node and yarn installed.

I tried to reinstall both node and yarn but I get the same error message. moreover I tried to remove the yarn chance via yarn cache clean but nothing seems to work.

The package.json contains the following:

The directory is organised in the following way:

21 Answers 21

There is no start command inside the scripts of the package.json file.

Maybe you want to run the test command instead — npm test / yarn test ?

Solved it thanks to the insight of the user: Tsvetan Ganev.

I was trying to run a command that it is not in my scripts. Specifically, yarn start is not in the scripts part of the file package.json . To solve the issue I added the following line in scripts

You can also try to run first npm install and then npm run or first yarn and then yarn start

I had the same issue start command not found. I followed below instruction to recreate react app

After installing yarn start will work.

I had this problem. I figured the best way is this.

1. npm i -g create-react-app
2. create-react-app my-react-app //or whatever you want your project to be
3. cd my-react-app
4. yarn start

I got the same error message «start» command not found. My issue got resolved by following the below mentioned steps.

-open the folder in which you want to create the app using terminal then type these commands:

1. npm uninstall -g create-react-app
2. npx create-react-app FolderName

(This will automatically install the latest create-react-app version)

-Then run the command yarn start and it will work.

Adding this to package.json worked for me

If you are using create-react-app and encountered this error, chances are you did not install create-react-app successfully.

Try removing globally installed create-create-app as explained below.

check your package.json that has «start» scripts. if you just have dependency list, make sure you have the following on the package.jons

otherwise run this on the folder where package.json is

error Command «start» not found.

theia should start on port 8080 minimally.

If you get error Command «start» not found. after creating new project using create-react-app you most probably would have created the app using npm .

To do it correctly delete the directory of the project and recreate the project using yarn with the following command

After that yarn start works perfectly fine.

i got the same issue. it cusses you have installed packages in wrong directory.

in cmd terminal:-(D:\PROJECT)=> my cmd file path shows

(when you enter this command it will create new file named app-react . then you have to go into the app-react file . use this command to go to the that file «cd app-react» then enter. you will see cmd path )

then install other yarn packges

then yarn start

if it is won’t open check yarn package installed using this command

for install yarn

I had a similar problem while I have «start» script in my package.json . Eventually, I figured out that I had not saved the package.json , so I got this error. Obviously, after saving the package.json the problem was resolved.

This issue happens when file «package.json» will gets deleted or changed. Please check your «package.json» file.

It may sound silly, but I was having this same problem and all I did was close the program (vscode), and reopen it. I made sure it was inside the correct project folder (web) and did the process again. It worked. In my case it was just a lack of attention.

I hope your problem is as simple as mine.

i solve the problem whit this: Since create-react-app 3.3.0 it’s not longer recommended to use a global installation of CRA.

However, after following the recommended way, uninstalling CRA globally and using npm,I ran into the following problem for my new React project:

A template was not provided. This is likely because you’re using an outdated version of create-react-app.

It seems like CRA wasn’t properly uninstalled. I had to do the following:

After uninstalling it with npm uninstall -g create-react-app, check whether you still have it «installed» with which create-react-app on your command line. If it returns something (e.g. /usr/local/bin/create-react-app), then do a rm -rf /usr/local/bin/create-react-app to delete manually.

Afterward, I was able to use npx create-react-app my-app with the latest version of CRA where I would have the default template for the src/ folder

Источник

Yarn install command error No such file or directory: ‘install’

I am installing sylius bundle and while install sylius I need to run yarn install So While i run command

ERROR: [Errno 2] No such file or directory: ‘install’

17 Answers 17

I had the same issue on Ubuntu 17.04.

This solution worked for me:

then

result:

Hope that it will help you.

I had the same issue on Ubuntu 18.04. This was what worked for me:

I removed cmdtest and yarn

Install yarn globally using npm

Note: This solution works well on Ubuntu 16.04 , Ubuntu 17.04 and Ubuntu 18.04 .

Try to remove the existing cmdtest and yarn (which is the module of legacy black box command line tool of *nix systems) :

Install it simple via npm

Now yarn is installed. Run your command.

I hope this will work. Cheers!

Edit:

Do remember to re-open the terminal for changes to take effect.

With kudos to all the answers that correctly suggest removing the Ubuntu yarn package and installing Yarn through NPM, here is a detailed answer with explanation (and, be warned, opinions):

The reason for the No such file or directory error from yarn install is that you are not using the «correct» Yarn: the software you get when you install yarn using the Ubuntu software sources is the «yarn» scenario testing tool from the cmdtest blackbox testing suite. This is likely not what you meant as Yarn is also a popular development lifecycle tool for Javascript application (similar to Make, Maven and friends).

The Javascript Yarn tool is not available from Ubuntu software sources but can be installed by NPM (which is another development lifecycle tool that Yarn aims to replace — so that’s awkward. ).

To make Yarn available in Ubuntu, start by removing cmdtest and its tools:

Then make sure NPM is installed:

Then use NPM to install Yarn:

Note: using npm install -g will install a Javascript package for your current user account, which should be fine for most purposes. If you want to install Yarn for all users, you can use sudo for the NPM command, but that is not recommended: NPM packages are rarely audited for security in the context of a multi-user operating system and installing some packages might even break when installing them as «root». NPM used to warn against running it with sudo and the main reason it is not doing so today is that it annoys people that use sandboxed «root-like» environments (such as Docker) for building and deploying Javascript applications for single-user servers.

Источник