Skip to content
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

node-sass compilation error #295

Open
todrobbins opened this issue Nov 6, 2019 · 0 comments · May be fixed by #300
Open

node-sass compilation error #295

todrobbins opened this issue Nov 6, 2019 · 0 comments · May be fixed by #300
Labels
v1 wontfix v1 bugs that will not be prioritized for fix, in favor of v2

Comments

@todrobbins
Copy link

Hi there!

I just tried running the browser on my end, and ran into this error:

Failed to compile.

./src/styles/main.scss
Module build failed: Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (72)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.5.3

Anyone run into this before? Looks like an upstream issue, but it's preventing the app from loading in the browser.

My specs:

  • node v11.0.0
  • yarn v1.19.1
julienr pushed a commit to julienr/oam-browser that referenced this issue Apr 10, 2020
…(13)

This fixes a build issue due to [email protected] which doesn't seem to build
anymore on recent node version. Webdriver is depending on fiber, so updating
the webdriver packages fixes this.

Since newer versions of webdriver have removed browser.clik in favor of
$(selector).click(), this also updates the integration tests for this change.

Closes hotosm#295
@julienr julienr linked a pull request Apr 10, 2020 that will close this issue
2 tasks
@cgiovando cgiovando added the v1 wontfix v1 bugs that will not be prioritized for fix, in favor of v2 label Apr 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1 wontfix v1 bugs that will not be prioritized for fix, in favor of v2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants