Issue #365 - Added option to override package manager.

[RobinTo]

Implemented parameter for create-razzle-app to override package manager, could resolve #365 if useable.

create-razzle-app my-project -p npm

Command	Info	Valid values
-p --packageManager	Override package manager, default to yarn.	npm, yarn

Tested this on mac using

• npx ./razzle/packages/create-razzle-app/bin/create-razzle-app test-razzle-project -p npm
• cd test-razzle-project
• npm start

If the option is not supplied it defaults to old behaviour, otherwise checks that it is one of yarn or npm, and defaults to old behaviour if not. Could remove check for yarn or npm if you want to enable any value to be used.

I want to be able to keep supporting projects that use yarn, while favoring npm for new projects.

Due to the sentence above I was unsure wether to set the default to npm, but currently it default to yarn as previously done. Could be changed if desired.

I hope you find this useful, even though the issue was marked as low priority.

Some yarn lockfiles unrelated to my modifications appear to have many changes. I'm not very familiar with the inner workings of yarn, but I suspect it might be due to newer yarn version when I ran the initial yarn setup?

[jariz]

I'm slowly seeing the JS hemisphere moving back to npm, but correct me if I'm wrong.
Eitherway, yarn was the previous default so probably best to keep it that way.

[jariz]

@RobinTo Can you update all readme's? There are more than 2.
I know this is kind of annoying but it's something that's being worked on (#409)

[RobinTo]

Of course, all the relevant readme files should now be updated.

[jaredpalmer]

Not sure why lockfiles are in this commit. May need to open a new PR

[jaredpalmer]

Which***

[jaredpalmer]

Is there a way to automatically tell based on whether user has called this with npx or yarn create?

[RobinTo]

I fixed the spelling error. Let me know if you want me to open a new pull request where I reset the lockfiles to the versions present on current master.

As far as I could see with some light searching, there is no way to detect if it was done through yarn create or directly, since according to https://yarnpkg.com/lang/en/docs/cli/create/ yarn create is equal to

$ yarn global add create-react-app
$ create-react-app my-app

where the end result is the same as if you had installed create-react-app globally with any packagemanager and ran the command directly. If you have any suggestions where to look for making it work, please let me know though and I'd be happy to look into it further.

[jariz]

I've done a little research by running yarn create and sadly process.argv returns the same as it would when directly running the script.
On top of that process.ppid is set to undefined, so no way to get information about who started the script either.

So, short answer to @jaredpalmer's question: Nope.

[jariz]

Scratch that, ppid only exists in 9.2+ and it does appear to return the yarn pid, but then again, that version has only been out for 2 months.
So, I think this is kind of out of scope for now, unless we're willing to do all sorts of crazy platform specific hacks.

[jaredpalmer]

Nice

[stale]

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]

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