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

Support Node v18 for build #1285

Conversation

heapifyman
Copy link
Contributor

@heapifyman heapifyman commented Nov 13, 2022

closes #1284

Remove dependency "fibers", which does not work with node 16 and above - see https://github.com/laverdet/node-fibers#readme.

Disable use of "fibers" in "sass-loader" according to https://webpack.js.org/loaders/sass-loader/#string.

Update instructions to setup development environment in README. It should be possible to build the project with nodejs 18 (current LTS version) now.

I've tried npm run build and npm run watch, and both succeeded with out errors. I haven't tried actually running the project in Android Studio, for example.

Remove dependency "fibers", which does not work with node 16 and above - see https://github.com/laverdet/node-fibers#readme.
Update instructions to setup development environment in README
- In the root of your floccus repo, run `npm install && npm install -g gulp`
- Run `gulp` to build
- Find out more on how to develop browser extensions here: <https://extensionworkshop.com/>
- Install the [latest LTS version of node.js](https://nodejs.org/en/download/).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we just update this to v18 instead of the generic "latest lts"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My idea was: with "latest LTS" one does not have to update the README again when switching from v18 to v20.

And I thought it makes sense to keep the project aligned with the current active LTS version of nodejs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW, should the actions in .github/workflows/ be updated to use node v18?

@marcelklehr marcelklehr changed the title closes #1284 Support Node v18 for build Nov 13, 2022
@marcelklehr marcelklehr merged commit 1f99f75 into floccusaddon:develop Nov 13, 2022
@heapifyman heapifyman deleted the fix/1284-instructions-in-setting-up-a-dev-environment-are-not-working branch November 13, 2022 19:15
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 14, 2023
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.

Instructions in "Setting up a dev environment" are not working
2 participants