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

fix(flow): export flow definitions in the released bundle and fix the npm ignore too restrictive #115

Merged
merged 1 commit into from
Jul 24, 2017

Conversation

armandabric
Copy link
Collaborator

No description provided.

@armandabric armandabric self-assigned this Jul 24, 2017
@@ -4,7 +4,7 @@
"description": "Turn a ReactElement into the corresponding JSX string.",
"main": "dist/index.js",
"scripts": {
"build": "babel ./src/ --ignore=*.spec.js --source-maps --out-dir ./dist/",
"build": "babel ./src/ --ignore=*.spec.js --source-maps --out-dir ./dist/ && flow-copy-source -v --ignore=*.spec.js src/ dist/",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flow have an experimental command flow gen-flow-files to generate each file definition, but it's really experimental and failed too many times. So for now, we use the flow-copy-source tricks to have the flow definition exported with the library

@vvo vvo merged commit c4f91b9 into algolia:master Jul 24, 2017
@armandabric armandabric deleted the fix/flow-release branch July 24, 2017 11:52
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