-
Notifications
You must be signed in to change notification settings - Fork 184
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
Export default options so other dependent packages can test against changing properties #631
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,4 +20,5 @@ require.extensions['.md'] = | |
module.exports = { | ||
parseCliArgs, | ||
run, | ||
defaultOptions, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think you'll need to import this first? Like: const defaultOptions = require("./defaultOptions").default; Up at the top? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually this should fail travis with a linter violation. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was just testing the CI... Making sure it was still working correctly :) |
||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this is great.
We've gone back and forth here. It's nice to factor out devDependencies into the repo root to cut down on bootstrap time and storage requirements. But for modules where we use the "bin" script that breaks things. In this case I think adding it back into the package is the right move.
Eventually I'd like to have a
lerna bootstrap --hoist-external
or something that will let us define deps where they're actually used but then install them at the root and link bin scripts in where needed. Some day. :)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm missing the correct dev entry point... but when I cloned and then ran
npm run bootstrap
I hit the same gulp error.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we probably have other packages that will need similar treatment. 😬