Skip to content

Conversation

@JosefBredereck
Copy link
Contributor

@JosefBredereck JosefBredereck commented Oct 18, 2020

While changes were made to the package resolving, some errors appeared. This should fix these errors.

Closes #1157
Closes #1247
Closes #1257

Summary of changes:
Updated execa
Added CWD to the installation of packages

@coveralls
Copy link

coveralls commented Oct 18, 2020

Coverage Status

Coverage remained the same at 76.752% when pulling bd2b632 on feature/fix-create-script into 1fd6b45 on dev.

@JosefBredereck JosefBredereck removed the request for review from ringods October 18, 2020 17:40
@JosefBredereck JosefBredereck marked this pull request as draft October 18, 2020 17:40
@JosefBredereck JosefBredereck marked this pull request as ready for review October 18, 2020 17:52
@sghoweri
Copy link
Contributor

sghoweri commented Nov 9, 2020

@JosefBredereck @ringods what's the status on this one?

Is there something holding this back from getting released or can we get this hotfix out the door ASAP?

Asking for a friend (CC @bradfrost)! 😉

@JosefBredereck
Copy link
Contributor Author

@sghoweri from my side its ready.

@ringods
Copy link
Contributor

ringods commented Nov 10, 2020

@JosefBredereck if this makes sure that npm create is no longer running in a temporary folder, but from the current folder, then I expect my workaround mentioned here is no longer needed, right?

If this fixes this, then all fine by me too.

@JosefBredereck
Copy link
Contributor Author

Yes exactly that it is doing.

@JosefBredereck JosefBredereck merged commit 3917c42 into dev Nov 12, 2020
@JosefBredereck
Copy link
Contributor Author

@sghoweri @ringods that did not fix it (╯°□°)╯︵ ┻━┻
Sadly
I will investigate further

@JosefBredereck JosefBredereck deleted the feature/fix-create-script branch January 12, 2021 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

5 participants