search

glslify / glsl-tokenizer

r/w stream of glsl tokens
MIT License
51 stars 6 forks source link

test does not work #9

Closed dy closed 5 years ago

dy commented 8 years ago

Hi! I’ve cloned and made npm install, but running tests fails with 2 errors:

  glsl-tokenizer: invalid characters
    √ does not hang!
    √ collects all expected "operator" characters

  tests 5
  pass  3
  fail  2

  Failed Tests: There were 2 failures

    × glsl-tokenizer/string matches exactly the expected output
    × glsl-tokenizer/stream matches exactly the expected output

npm ERR! Test failed.  See above for more details.

Is that ok? json-diff shows at about a hundred diffs for that matter, so seems that fixture is old or something.

mattdesl commented 8 years ago

It seems pretty odd. What node/npm version? I just tested again with a fresh install on 2.1.0 and all tests are passing for me.

mattdesl commented 8 years ago

btw – I'm on node@5 and npm@2.14.12

dy commented 8 years ago

npm@3.7.2, node@5.5.0, win7. Wonder where the issue is - in the environment or in tokenizer itself

dy commented 8 years ago

in some reason glslify returns source code with double newlines \n\n in place of single newlines \n

dy commented 5 years ago

Fixed.