RFC: Binary Coverage Matrix #655

am11 · 2015-02-09T08:52:45Z

A module must be rebuilt whenever NODE_MODULE_VERSION changes. It changed from joyent/node 0.10 -> joyent/node 0.11, from joyent/node 0.11 -> iojs/io.js 1.0, and atom/atom-shell has its own fork going with yet another NODE_MODULE_VERSION.

we need to confine a binary coverage matrix for the most used versions of runtimes (related: #602 (comment)).

Updated:

The current version of node-sass is ~~v2.0.0-beta~~ v2.0.1 and the distributable binary availability of node-sass is given below:

Availability	Runtime	Version `NODE_MODULE_VERSION`	Platform	Architecture
	atom-shell	0.21	Linux	ia32
	atom-shell	0.21	Linux	x64
	atom-shell	0.21	Mac	x64
	atom-shell	0.21	Windows	ia32
	atom-shell	0.21	Windows	x64
	io.js	1.2	FreeBSD	ia32
	io.js	1.2	FreeBSD	x64
x	io.js	1.2	Linux	ia32
x	io.js	1.2	Linux	x64
x	io.js	1.2	Mac	x64
	io.js	1.2	Solaris	ia32
	io.js	1.2	Solaris	x64
x	io.js	1.2	Windows	ia32
x	io.js	1.2	Windows	x64
	node.js	0.12	FreeBSD	ia32
	node.js	0.12	FreeBSD	x64
x	node.js	0.12	Linux	ia32
x	node.js	0.12	Linux	x64
x	node.js	0.12	Mac	x64
	node.js	0.12	Solaris	ia32
	node.js	0.12	Solaris	x64
x	node.js	0.12	Windows	ia32
x	node.js	0.12	Windows	x64
	node.js	0.10	FreeBSD	ia32
	node.js	0.10	FreeBSD	x64
x	node.js	0.10	Linux	ia32
x	node.js	0.10	Linux	x64
x	node.js	0.10	Mac	x64
	node.js	0.10	Solaris	ia32
	node.js	0.10	Solaris	x64
x	node.js	0.10	Windows	ia32
x	node.js	0.10	Windows	x64

Note 1: atom-shell does not support FreeBSD and Solaris?
Note 2: This matrix will eventually be added to wiki and we will keep the coverage matrix up to date for the current version of node-sass.

The text was updated successfully, but these errors were encountered:

xzyfer · 2015-02-09T09:54:53Z

@am11 will we need to change the install script and node-sass-binaries to handle the different combinations?

i.e. will node 0.10.x binaries work with node 0.12.x and atom 1.x etc...

am11 · 2015-02-09T10:01:30Z

@xzyfer Yes. It would probably be something like: linux-x64-node-0.10.

Turbo87 · 2015-02-09T18:24:17Z

@am11 wouldn't it be better to put the matrix into the https://github.com/sass/node-sass-binaries README instead of the wiki? that way it would it could always reflect the current state of the repo, you get a history for free and linking to it isn't much harder than linking to the wiki.

am11 · 2015-02-09T19:36:04Z

@Turbo87, I think it would make more sense to add it to node-sass-binaries repo's README and a reference in node-sass' README.

In node-sass' README, we do not want to deliver the message as if it is some kind of set in stone limitation. User can manually build binaries on other platforms with various versions of runtimes. This (incomplete) matrix is only showing the binaries which we might be distributing OOTB.

Turbo87 · 2015-02-09T19:39:23Z

@am11 I know that, and I don't think it will be controversial if you put it exactly like that in the README next to the matrix too.

Martii · 2015-02-09T19:53:17Z

some kind of set in stone limitation.

Matrices are usually just denoting what's currently supported and not always set in stone. Anyone familiar with node packages knows that things change. Our project for example uses exact semver releases.

User can manually build binaries on other platforms with various versions of runtimes.

Our node host provider won't allow this as I previously mentioned over at the node-sass-binaries repo issues... our provider just happens to be joyent maintained as well.

As a potential further solution for displaying the matrices there is always GH io pages. That could be a common place to bring multiple repos together.

am11 · 2015-02-10T07:09:59Z

Super awesome @xzyfer for Mac binaries! 👍

Keep them coming! 😎

I am trying to figure out a sanest way to differentiate between runtimes, which is yet to be discovered (see nodejs/node-gyp#564 (comment)). I will then update our scripts/{et al.}.

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: <undefined>.

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 · 2015-02-11T11:45:42Z

@xzyfer, I am building the Windows binaries now for node.js (v0.10 and v0.12) and io.js (v1.1).
Would you rebuild the binaries for Mac as well; targeting the same (sub) matrix?

Note the last batch of commits has a minor change in binding code, hence rebuild the binary for node.js v0.10 and v0.12 is required.

Note 2: you can use nvm to switch between node.js or io.js versions (without installing them manually).

Once this step is done, I will apply the (LibSass gcc 4.4.7) patch and build Linux binaries on CenOS 5.11.

* node.js v0.10 ia32. * node.js v0.10 x64. * node.js v0.12 ia32. * node.js v0.12 x64. * io.js v0.12 ia32. * io.js v0.12 x64. PR URL: sass#28. Related Issue: sass/node-sass#655.

am11 · 2015-02-12T04:28:20Z

With v2.0.0, here is the state of coverage matrix: https://github.com/sass/node-sass-binaries/releases/tag/v2.0.0.

@Turbo87, would you like to send a PR for moving the updated matrix to README, the way you proposed?

browniefed · 2015-02-12T04:32:14Z

👍 Yaye

Turbo87 · 2015-02-12T08:26:50Z

@am11 sure, why not.

as suggested in sass/node-sass#655

am11 · 2015-02-12T14:36:54Z

Updated the matrix for v2.0.1 in first post.

saper · 2015-03-08T20:37:31Z

iojs 1.4.1 has upgraded v8 to 4.1.0.21 due to undisclosed security bug ( nodejs/node#952 ) - https://code.google.com/p/chromium/issues/detail?id=430201 (embargoed).

am11 · 2015-03-16T03:30:16Z

The information in the original post is outdated.

For v3.0.0-alpha.0 (rebooted preview), please refer to node-sass-binaries repo's readme: https://github.com/sass/node-sass-binaries/blob/master/README.md.
(summary: io.js v1.0.0-v1.5.1 are supported for Linux, Mac and Windows and FreeBSD is available for node.js v0.12)

Once we refactor the docs (#730), we will most probably bring the coverage status to node-sass readme.

Thanks for your comments.

saper · 2015-05-04T21:43:15Z

So, we now have io.js 2.0.0, which defines NODE_MODULE_VERSION to 44

Fix error for some selectors with interpolants

This was referenced Feb 9, 2015

Any news when stable 2.0 will be released? #602

Closed

io.js 1.1 support #627

Closed

Why does node-sass downloads\builds the binding on each npm install? #654

Closed

am11 mentioned this issue Feb 9, 2015

node-sass@1.2.3 postinstall failing on Ubuntu 12.04.5 #550

Closed

am11 added the Discussion - Proposal label Feb 9, 2015

This was referenced Feb 10, 2015

Add 2.0.0 Darwin x64 node 0.10 binary sass/node-sass-binaries#35

Merged

Add 2.0.0 Darwin x64 node 0.12 binary sass/node-sass-binaries#34

Merged

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

dbd4965

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: <undefined>.

am11 mentioned this issue Feb 10, 2015

Build: Produces identifiable binary name #657

Merged

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

b6ee845

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

b66aa3b

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

f5f05cd

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

a919a7a

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

57c9078

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

b2a5443

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

8cf4540

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

269f4b4

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

b8a6309

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

0923568

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

2be25ba

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 added a commit to am11/node-sass that referenced this issue Feb 10, 2015

Build: Produces identifiable binary name.

4b5ebaf

The new format is: {platform}-{arch}-{runtime}-{major.minor} where major and minor version belong to the runtime. Related Issue: sass#655. PR URL: sass#657.

am11 mentioned this issue Feb 11, 2015

Question: Is there a way to emit current matrix information in user code? appveyor/ci#139

Closed

Turbo87 added a commit to Turbo87/node-sass-binaries that referenced this issue Feb 12, 2015

README: Add compatibility/coverage matrix

0efda91

as suggested in sass/node-sass#655

This was referenced Feb 12, 2015

README: Add compatibility/coverage matrix Turbo87/node-sass-binaries#1

Closed

README: Add compatibility/coverage matrix sass/node-sass-binaries#41

Merged

am11 mentioned this issue Feb 13, 2015

support install with OS_ARCH hakobera/nvmw#41

Merged

am11 added this to the Unknown milestone Feb 13, 2015

chrisbenson mentioned this issue Feb 14, 2015

'ember g ember-cli-foundation-sass' not working on io.js 1.2.0 nadavshatz/ember-cli-foundation-sass#20

Closed

bnb mentioned this issue Feb 17, 2015

Evangelism: Weekly Update Feb 20th nodejs/iojs.org#188

Closed

yous mentioned this issue Feb 22, 2015

Added: 2015년 2월 20일 주간 뉴스 (resolve #25) nodejs/nodejs-ko#28

Merged

am11 added the npm build label Feb 23, 2015

This was referenced Mar 2, 2015

Refactoring docs #730

Open

Support clang C++ library #733

Closed

Time to ship 3.0.0? #710

Closed

am11 closed this as completed Mar 16, 2015

stephenplusplus mentioned this issue Apr 20, 2015

Update CRC module to SSE4_CRC32 v3.1.0 googleapis/google-cloud-node#488

Merged

xzyfer removed this from the Unknown milestone Sep 17, 2015

renovate bot mentioned this issue Jun 6, 2021

Update dependency node-sass to v6 - autoclosed zce/SmartControl#49

Closed

1 task

jiongle1 pushed a commit to scantist-ossops-m2/node-sass that referenced this issue Apr 7, 2024

Merge pull request sass#655 from xzyfer/fix/issue_641

2e48c07

Fix error for some selectors with interpolants

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RFC: Binary Coverage Matrix #655

RFC: Binary Coverage Matrix #655

am11 commented Feb 9, 2015

xzyfer commented Feb 9, 2015

am11 commented Feb 9, 2015

Turbo87 commented Feb 9, 2015

am11 commented Feb 9, 2015

Turbo87 commented Feb 9, 2015

Martii commented Feb 9, 2015

am11 commented Feb 10, 2015

am11 commented Feb 11, 2015

am11 commented Feb 12, 2015

browniefed commented Feb 12, 2015

Turbo87 commented Feb 12, 2015

am11 commented Feb 12, 2015

saper commented Mar 8, 2015

am11 commented Mar 16, 2015

saper commented May 4, 2015

RFC: Binary Coverage Matrix #655

RFC: Binary Coverage Matrix #655

Comments

am11 commented Feb 9, 2015

Updated:

xzyfer commented Feb 9, 2015

am11 commented Feb 9, 2015

Turbo87 commented Feb 9, 2015

am11 commented Feb 9, 2015

Turbo87 commented Feb 9, 2015

Martii commented Feb 9, 2015

am11 commented Feb 10, 2015

am11 commented Feb 11, 2015

am11 commented Feb 12, 2015

browniefed commented Feb 12, 2015

Turbo87 commented Feb 12, 2015

am11 commented Feb 12, 2015

saper commented Mar 8, 2015

am11 commented Mar 16, 2015

saper commented May 4, 2015