Have you read the Contributing Guidelines on issues?
Prerequisites
Description
See demo here: https://du0ui.sse.codesandbox.io/docs/intro
If you use @docusaurus/remark-plugin-npm2yarn and your code snippet is set like this:
```sh npm2yarn
npm init wdio ./foo
```
I would expect that it would transform the yarn version to yarn create wdio ./foo.
Steps to reproduce
- create a standard docusarus page
- add
@docusaurus/remark-plugin-npm2yarn plugin
- add example as mention above
Expected behavior
I would expect that it would transform the yarn version to yarn create wdio ./foo.
Actual behavior
It displays npm init wdio ./foo and yarn init wdio ./foo which results in the attempt of creating a new yarn package rather than running the create-wdio starter package.
Your environment
- Public source code:
- Public site URL:
- Docusaurus version used:
- Environment name and version (e.g. Chrome 89, Node.js 16.4):
- Operating system and version (e.g. Ubuntu 20.04.2 LTS):
Reproducible demo
https://codesandbox.io/s/nice-fire-du0ui?file=/docusaurus.config.js
Self-service
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clearoryarn clearcommand.rm -rf node_modules yarn.lock package-lock.jsonand re-installing packages.Description
See demo here: https://du0ui.sse.codesandbox.io/docs/intro
If you use
@docusaurus/remark-plugin-npm2yarnand your code snippet is set like this:I would expect that it would transform the yarn version to
yarn create wdio ./foo.Steps to reproduce
@docusaurus/remark-plugin-npm2yarnpluginExpected behavior
I would expect that it would transform the yarn version to
yarn create wdio ./foo.Actual behavior
It displays
npm init wdio ./fooandyarn init wdio ./foowhich results in the attempt of creating a new yarn package rather than running thecreate-wdiostarter package.Your environment
Reproducible demo
https://codesandbox.io/s/nice-fire-du0ui?file=/docusaurus.config.js
Self-service