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

Enabling use of ebnf-parser in production code #5

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

PawelDefee
Copy link

"npm install ebnf-parser" will now install dependencies from npm repository. Also changed jison reference to point to npm release.

Use case / why this would be good:

An open-source project I want to use, node-proto2json, depends on jison. It has not been updated for a while and I wanted to bring all its dependencies up to date. Since ebnf-parser was split out from jison a long time ago, this meant some code changes and package.json update.

However, ebnf-parser defines its dependencies as "dev" only so that installing it as dependency via npm repository will not work correctly. This pull request aims to fix this issue.

…of package.json. Changed

path to jison module to point to latest official release instead of GitHub URL.
@dfreeman
Copy link

dfreeman commented Oct 5, 2015

@PawelDefee Ran into the same thing you did with lex-parser missing, but it looks like jison should stay a dev dependency – it only appears to be used by the Makefile and in tests.

@Qix-
Copy link

Qix- commented Nov 2, 2015

+1 can this get merged? :)

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.

3 participants