CLI Error: react-static-create(1) does not exist
See original GitHub issueDescribe the bug The CLI command
react-static create
shows an error.
To Reproduce I just installed react-static globally using
yarn global add react-static
(latest version of yarn 1.10.1)
If I launch
react-static create
I receive the error
error: react-static-create(1) does not exist, try --help
The help command is the only which works.
I’m using Node 10.9.0 on a Mac with MacOS Sierra 10.12.6.
I fear it’s a problem with my environment, but other CLIs like create-react-app, gatsby or next work well.
Thank you, Matteo
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:19
Top Results From Across the Web
react-static | Yarn - Package Manager
If this is a problem, you can use the process.env.REACT_STATIC_THREAD === 'true' condition to detect if the instance is a threaded export slave...
Read more >can't resolve 'file-loader' | The AI Search Engine You Control
npm install sass-loader -D npm install node-sass -D. Open side panel. Can't resolve 'css-loader!autoprefixer-loader'. Asked May 9, 2018 • 1 votes 1 answer....
Read more >Build a Complete Jamstack App with CockroachDB and Netlify ...
Let's explore how to use React-Static to generate our static Jamstack application. This application will store data in a CockroachDB using ...
Read more >Gatsby vs. React Static vs. Next.js - IONOS Deploy Now
Gatsby is one of the more well-known React frameworks because it is very versatile and has a robust development team driving its growth....
Read more >Error: A column was specified that does not exist. 0. Failed to ...
0. Failed to execute (GeneratePathways). Error Message. In ArcGIS Pro, when running the Generate Pathways tool with ArcGIS Indoors, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yeah why is this closed… still happening. thanks for the workaround @luskin
I have the same problem… I also have found a workaround/resolution
It seems that it is indeed due to the installed symlink pointing to a relative path that is breaking as
commander
does not follow. If you execute the command directly it works… see workaround/solution below.Environment
Reproduce
Remove the global package
Check it is no longer available
Above should have no output
Add the global package
Check it is now available
Above should have output pointing to something like
/home/X/.local/bin/react-static
Try to create a project
Above fails with
error: react-static-create(1) does not exist, try --help
Check the command
Above outputs something like
/home/X/.local/bin/react-static -> ../../.config/yarn/global/node_modules/.bin/react-static
Note the
../../
in the symlink; it seems this is the problemTry using the command directly; so the command the symlink points to
The above works…
Workaround/Solution
Make the symlink absolute
Outputs:
/home/X/.local/bin/react-static -> /home/X/.config/yarn/global/node_modules/react-static/bin/react-static
The symlink is now absolute and the command works 😉
react-static create
@tannerlinsley postinstall hook? as it seems to be a problem with the
commander
package