Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Version 5.0 #2312

Merged
merged 23 commits into from
Nov 8, 2019
Merged

Version 5.0 #2312

merged 23 commits into from
Nov 8, 2019

Conversation

xzyfer
Copy link
Contributor

@xzyfer xzyfer commented Apr 3, 2018

See #2111

Features

Misc

Maybe

  • Official electron support

@xzyfer xzyfer self-assigned this Apr 3, 2018
@xzyfer xzyfer force-pushed the v5 branch 3 times, most recently from 72c51b2 to 0622e7b Compare April 3, 2018 09:48
@xzyfer xzyfer added the v5 label Apr 4, 2018
package.json Outdated Show resolved Hide resolved
@xzyfer xzyfer force-pushed the v5 branch 2 times, most recently from 6dfa324 to 37289ef Compare April 4, 2018 12:46
@YasharF YasharF mentioned this pull request Apr 28, 2018
realityking and others added 10 commits November 7, 2019 21:52
This was a non-standared feature in LibSass we had to support. It
is being removed in LibSass 3.6.0.

This prevents people from output their source directory.

See sass/libsass#2611
See #2184
See #2006
See #1933
See #1925
See #1867
See #1845
Four years ago there was a test that mutated `process.cwd` but
didn't correctly reset it. The altered global state resulted in
future tests having incorrect assetions. I only noticed this because
for some reason it manifested in failures in only _some_ Node
versions when N-API was being used.
@xzyfer xzyfer changed the base branch from master to next-major November 7, 2019 11:37
@xzyfer
Copy link
Contributor Author

xzyfer commented Nov 7, 2019

@nschonni @saper I've created the next-major branch. The plan is to merge all the 5.0 milestone changes into that branch so that we can start cutting 5.0 betas with the latest libsass, and trial N-API.

@xzyfer xzyfer merged commit e1735cb into next-major Nov 8, 2019
@saper
Copy link
Member

saper commented Nov 8, 2019

Is N-API here ready for the prime time? I think have already big changes in, let's not put too many...

@xzyfer
Copy link
Contributor Author

xzyfer commented Nov 8, 2019 via email

@saper
Copy link
Member

saper commented Nov 9, 2019

Sure the code works now - the question is can we release a new binding file with a new version number when the libuv gets upgraded (it gets upgraded pretty often, but rarely breaks compatibility).

I wrap my head around this: https://nodejs.org/api/n-api.html#n_api_implications_of_abi_stability

We include <uv.h> in src/callback_bridge.h and we need it. That probably means we have to check our compatibility with libuv via some other means.

@xzyfer
Copy link
Contributor Author

xzyfer commented Nov 9, 2019

N-API has async APIs we can use instead of direct libuv
https://nodejs.org/api/n-api.html#n_api_simple_asynchronous_operations

@saper
Copy link
Member

saper commented Nov 9, 2019

Yes, we should switch to that. Looks like a non-trivial rewrite to me :(

@xzyfer
Copy link
Contributor Author

xzyfer commented Nov 9, 2019 via email

@saper
Copy link
Member

saper commented Nov 9, 2019

But that means to me we should drop it if we want to kick 5.0 out of the door quickly. Sorry if I am feeling pushy and not contributing enough... :(

@xzyfer
Copy link
Contributor Author

xzyfer commented Nov 9, 2019 via email

@saper
Copy link
Member

saper commented Nov 9, 2019

Sure, I'll have a look at it too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants