Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use npx versus npm #222

Closed
blackfalcon opened this issue Sep 27, 2021 · 2 comments · Fixed by #265
Closed

Use npx versus npm #222

blackfalcon opened this issue Sep 27, 2021 · 2 comments · Fixed by #265
Assignees
Labels
Type: Documentation Documentation only changes Type: Feature New Feature
Milestone

Comments

@blackfalcon
Copy link
Member

Is your feature request related to a problem? Please describe.

One of the clear challenges with using the generator is ensuring that users have the latest version installed. There is tooling installed that tries to determine the latest version is installed, but it randomly fails, and tracking down why is really hard.

Describe the solution you'd like

Use npx versus npm install. npx will allow users to run the generator without installing locally. This also ensures that the latest version of the npm package is the one executed.

The scope of this update is mainly with documentation for install and use instructions.

Additional context

This update has little to no impact on how the generator is currently set up. I'd argue that we can lose the Please confirm you have the latest version installed question, which isn't really having any impact anyway.

We'd still want to support the versioning verification code as this is important when the generator is installed and working correctly.

@blackfalcon blackfalcon added Type: Documentation Documentation only changes Type: Feature New Feature auro-generator labels Sep 27, 2021
@blackfalcon
Copy link
Member Author

FYI... there is nothing stopping anyone from doing this right now. This issue is to discuss if we want to embrace this and how.

@settings settings bot removed the not-reviewed label Oct 12, 2021
@blackfalcon blackfalcon added the not-reviewed Issue has not been reviewed by Auro team members label Oct 13, 2021
@blackfalcon blackfalcon added this to the v3.11-rc milestone Nov 10, 2021
@blackfalcon
Copy link
Member Author

this work should be done at the same time as this #263

@blackfalcon blackfalcon removed the not-reviewed Issue has not been reviewed by Auro team members label Nov 11, 2021
@blackfalcon blackfalcon mentioned this issue Nov 11, 2021
8 tasks
@blackfalcon blackfalcon self-assigned this Nov 11, 2021
@blackfalcon blackfalcon linked a pull request Nov 11, 2021 that will close this issue
6 tasks
blackfalcon pushed a commit that referenced this issue Nov 16, 2021
# [3.11.0](v3.10.0...v3.11.0) (2021-11-16)

### Bug Fixes

* **demo:** remove offending code [#268](#268) ([e8b88bc](e8b88bc))
* **markdownmagic:** remove aurolabs version of readme from the commit back function ([1a636b7](1a636b7))
* reinstall jsdoc linter support ([f9db59c](f9db59c))
* **stylelint:** add stylelint-config-standard-scss as a dependency [#267](#267) ([2d45252](2d45252))

### Features

* **dev server:** update to support single shell for dev server [#225](#225) ([eb73188](eb73188))
* **node version:** automate management of node version [#262](#262) ([7325b14](7325b14))
* **node version:** automate management of node version [#262](#262) ([ff6d2d9](ff6d2d9))
* **npx:** update all docs to use npx command [#222](#222) ([657cc1e](657cc1e))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Documentation Documentation only changes Type: Feature New Feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant