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

feat: node 18 support, crawlee and bullseye #83

Merged
merged 9 commits into from
Aug 18, 2022

Conversation

vladfrangu
Copy link
Member

@vladfrangu vladfrangu commented Aug 16, 2022

@vladfrangu
Copy link
Member Author

Right off the bat I can see that nodejs 14 and 15 are probably to be removed if we want to move to actor sdk + crawlee... Is that ok? Are we ready for that?

@szmarczak
Copy link
Contributor

szmarczak commented Aug 16, 2022

Right off the bat I can see that nodejs 14 and 15 are probably to be removed if we want to move to actor sdk + crawlee... Is that ok? Are we ready for that?

I'd wait once people start using Node.js 18 more (a few weeks). Then there will be a drop-off in Node.js 14 users.
No strong opinions however, we can remove it as well.

Comment on lines +38 to +42
# Cleanup apt caches
RUN apt-get clean -y && apt-get autoremove -y \
&& rm -rf /var/lib/apt/lists/* \
&& rm -rf /src/*.deb

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this required?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's something we've done in all images to shave off some extra space from the redundant deb packages cached by apt (that said I never tried it with/without it so...maybe it's not? I could try it out and see if theres a size diff)

@B4nan
Copy link
Member

B4nan commented Aug 16, 2022

I would drop node < 16 right ahead. Why should we base this on usage of node 18? Also, the old images will be still there for people using v2. Using v3 requires node 16.

@pocesar
Copy link

pocesar commented Aug 16, 2022

this will also instantly fix this: nodejs/node#39400 and nodejs/node#32978

@B4nan
Copy link
Member

B4nan commented Aug 17, 2022

this will also instantly fix this: nodejs/node#39400 and nodejs/node#32978

fyi node 18 images will be opt in before lts is out, we will keep node 16 in the templates

Copy link
Member

@mnmkng mnmkng left a comment

Choose a reason for hiding this comment

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

LGTM. Please test how template build times look on the platform with these images. The target is < 1 min.

@pocesar
Copy link

pocesar commented Aug 17, 2022

the hardcoded NODE_VERSION=16 will make it possible to use :18 on Dockerfile? or is there a separate image that will be created?

node/package.json Show resolved Hide resolved
@vladfrangu
Copy link
Member Author

the hardcoded NODE_VERSION=16 will make it possible to use :18 on Dockerfile? or is there a separate image that will be created?

Yep! That's just the default value if not specified! If we specify NODE_VERSION=18 in CI we'll build a node 18 image

@vladfrangu vladfrangu merged commit d9b5abf into master Aug 18, 2022
@vladfrangu vladfrangu deleted the feat/node-18-and-bullseye-and-crawlee branch August 18, 2022 11:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants