You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, this is only able to parse a subset of possible Node.JS versions. We have started tagging our Node.JS builds with extended version numbers (e.g. 8.11.2+some-tag), which is valid according to the semver convention that Node.JS follows, but results in webpacker blowing up:
rake aborted!
ArgumentError: Malformed version number string 8.11.3+0-b20180704T02124290
/opt/lib64/ruby/2.4.0/rubygems/version.rb:208:in `initialize'
/opt/lib64/ruby/2.4.0/rubygems/version.rb:199:in `new'
/opt/lib64/ruby/2.4.0/rubygems/version.rb:199:in `new'
/tmp/build/vendor/bundle/ruby/2.4.0/gems/webpacker-3.5.3/lib/tasks/webpacker/check_node.rake:12:in `block (2 levels) in <top (required)>'
The text was updated successfully, but these errors were encountered:
It looks like the
webpacker:check_node
uses theGem::Version
parser to parse Node.JS versions:webpacker/lib/tasks/webpacker/check_node.rake
Line 12 in 4f5e1ac
Unfortunately, this is only able to parse a subset of possible Node.JS versions. We have started tagging our Node.JS builds with extended version numbers (e.g. 8.11.2+some-tag), which is valid according to the semver convention that Node.JS follows, but results in webpacker blowing up:
The text was updated successfully, but these errors were encountered: