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

chore: use npm command rather than meteor npm #5328

Merged
merged 1 commit into from
Jul 16, 2019

Conversation

aldeed
Copy link
Contributor

@aldeed aldeed commented Jul 16, 2019

Impact: minor
Type: chore

Issue

Running the .reaction/scripts/build.mjs Node script finds and loads all plugins. There was one Meteor dependency in this script, preventing it from working if you haven't installed Meteor in the environment.

Solution

The meteor npm i command this script runs in each plugin folder is changed to npm i. This means there will no longer be a Meteor layer ensuring that the correct version of NPM is used. However, we keep the version in the image consistent with the version that Meteor ships with, so this shouldn't be a problem.

Breaking changes

None.

Testing

Verify you can run node --experimental-modules ./.reaction/scripts/build.mjs without errors in an environment that doesn't have the meteor CLI available.

in loadPlugins

Signed-off-by: Eric Dobbertin <[email protected]>
@aldeed aldeed requested a review from rosshadden July 16, 2019 19:32
@aldeed aldeed self-assigned this Jul 16, 2019
@aldeed aldeed merged commit 110cccf into develop Jul 16, 2019
@aldeed aldeed deleted the chore-aldeed-use-standard-npm-to-load-plugins branch July 16, 2019 20:48
@kieckhafer kieckhafer mentioned this pull request Aug 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants