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

Webpack 5 support #266

Closed
virajsanghvi opened this issue Jul 8, 2020 · 22 comments
Closed

Webpack 5 support #266

virajsanghvi opened this issue Jul 8, 2020 · 22 comments

Comments

@virajsanghvi
Copy link

Hi, I was just wondering if there were plans to support webpack 5 or if that was going to wait until its official release. Thanks!

@edmorley
Copy link
Member

edmorley commented Jul 8, 2020

@virajsanghvi Hi! I'd be happy to accept a PR to add support before the webpack 5 final release. However I don't have much time to work on webpack-chain or Neutrino at any more, so we'd need someone from the community to open a PR :-)

@gpetrov
Copy link

gpetrov commented Oct 10, 2020

@edmorley Does this makes webpack-chain totally unusable with webpack 5? Or it is just that few new options are not supported bit it can read and write webpack 5 configs just as well?

@edmorley
Copy link
Member

@gpetrov The latter :-)

@gpetrov
Copy link

gpetrov commented Oct 10, 2020

Great to hear! I was just searching for a tool to read/write webpack config and webpack-chain seems to fit perfectly, but cooperation with webpack 5 is essential.

Could you identify a bit the parts that might need changes for webpack 5 - I will be glad to help out.

@edmorley
Copy link
Member

I would start by reading through:
https://webpack.js.org/blog/2020-10-10-webpack-5-release/

...and seeing if there are any options added/removed that are essential for a webpack config, and not currently set-able with webpack-chain :-)

@concubicycle
Copy link

concubicycle commented Mar 4, 2021

I think this is a duplicate - I saw another issue for Webpack 5 support here. But regardless, it's a shame we don't have it yet. there are some libraries like postcss-loader which now depend on Webpack 5, and to get them working with Neutrino, you have to install an older version of the loader. I might give this a go if I have time..

@edmorley
Copy link
Member

edmorley commented Mar 4, 2021

Hi! I'm not actively working on any project that uses webpack, so haven't used Neutrino or webpack-chain for some time. As such it's hard to justify spend time maintaining them. I'd hoped there would be more interest from the rest of the community in helping with maintenance (particularly given the Vue ecosystem uses webpack-chain), but there hasn't been so far.

For webpack 5 support to happen, someone will need to volunteer to open a PR :-)

@sodatea
Copy link

sodatea commented Mar 26, 2021

Hi, @edmorley I'm maintaining Vue CLI and I would love to help triage issues and review PRs in this repository :)

As for actual coding tasks, I may not have large pieces of time to dive into the codebase. But I'll try my best to help.

@edmorley
Copy link
Member

edmorley commented Mar 26, 2021

@sodatea Thank you for the offer to help. Adding webpack 5 support will likely require a few people to help out - someone to open a PR and someone who is up to date with webpack 5 changes to review. Once the PR is open and an initial review from someone else has taken place, I'm happy to have one last glance over before merging and releasing a new webpack-chain version - however just to set expectations, I won't have time to open the PR myself or perform the primary review. However I will definitely do anything I can on the release side.

@edmorley
Copy link
Member

Also given the Travis CI situation (no more credits being given to OSS projects), someone will need to convert the CI to either GitHub Actions or Circle CI. The Neutrino project looks like it's going to start using GitHub Actions (neutrinojs/neutrino/pull/1663) so that might be the best option. I don't have time to work on this, but would be able to review a PR.

@edmorley edmorley added this to the webpack-chain 7 milestone Mar 26, 2021
@edmorley edmorley pinned this issue Mar 26, 2021
@concubicycle
Copy link

I'm up for it.. I have a little time these days.

@githoniel
Copy link
Contributor

@concubicycle how is your work now?

I will implement it because my company's project also needs this

@concubicycle
Copy link

@concubicycle how is your work now?

I will implement it because my company's project also needs this

Ah, my bad, I've been really busy this past month. Started a job

@githoniel
Copy link
Contributor

@concubicycle how is your work now?
I will implement it because my company's project also needs this

Ah, my bad, I've been really busy this past month. Started a job

never mind, let me try this

@januwA
Copy link

januwA commented Jul 15, 2021

Now many loaders have been updated to webpack 5

@githoniel
Copy link
Contributor

githoniel commented Jul 15, 2021

Now many loaders have been updated to webpack 5

Although my PR hasn't been merged yet, it work fine,edmorley has been very busy lately

@closertb
Copy link

closertb commented Nov 1, 2021

Now many loaders have been updated to webpack 5

Although my PR hasn't been merged yet, it work fine,edmorley has been very busy lately

is plan to build a beta version recently ??

@kingyue737
Copy link

Hi, @edmorley I'm maintaining Vue CLI and I would love to help triage issues and review PRs in this repository :)

As for actual coding tasks, I may not have large pieces of time to dive into the codebase. But I'll try my best to help.

Is chainWebpack of vue.config.js still available in vue cli5?

@yorickshan
Copy link

any updates?

@chemparparokke
Copy link

chemparparokke commented Mar 29, 2023

Is chainWebpack of vue.config.js still available in vue cli5?

As I see, it is still available, but missing some config features. For example it is impossible now to set externalsPresets using webpack-chain. Maybe there are more limitations 🤔

@edmorley
Copy link
Member

I marked the wepack-chain package on npmjs.org as deprecated on 18th December, to more accurately reflect the current state of the project. The package can still be used but now a deprecation warning is shown when it is installed.

@edmorley edmorley closed this as completed Feb 3, 2024
@edmorley
Copy link
Member

edmorley commented Feb 3, 2024

Closing since this project is no longer maintained:
#358

@edmorley edmorley closed this as not planned Won't fix, can't repro, duplicate, stale Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests