-
Notifications
You must be signed in to change notification settings - Fork 36
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
Error when building with rollup #25
Comments
Okay, I found the problem. jison was, for a time, not generating strict mode compatible output. It seems that this was fixed in jison 0.4.16, and route-parser depends on 0.4.17. Has the compiled-grammar file been regenerated since then? I think that would solve this problem. |
I just regenerated compiled-grammar.js and nothing changed. I know I'm on the latest version of jison, and I checked the fix was present in it's code, but it still keeps generating a file with the Does anyone know what could be going on here? |
So apparently that commit only fixed the problem if the As an interim fix, I simply added a line to remove the label manually in the This produces output that works in strict mode. You can see the changes in #26. There might be a better way to fix this, but this works for now. I'm trying to see if anyone from jison can fix the underlying problem. |
On a side note: can you push bump the patch version and publish the new code? I'm depending directly on a git commit right now. |
great insight into this issue. Please can you explain how to provide the token-stack option to JISON. I have no idea! thanks |
@danday74 Or you can include it directly in the grammar object:
|
I keep getting this error when trying to bundle a library with rollup. The library depends on route-parser.
I can't tell what's actually wrong in the
compiled-grammar.js
file at 163:8 but the whole file looks a bit strange. I assume because it was created by a grammar generator.Is it violating some syntactic rules that the rollup parser enforces? Maybe I should open an issue with jison. Any thoughts?
The text was updated successfully, but these errors were encountered: