applicationtriada.blogg.se - Npm upgrade webpack

#Npm upgrade webpack code

Migrating from NPM to Yarn - First step towards a new journeyĪfter reading about Yarn, the team was really curious to play with this yet new package manager aka dependency manager. The task which took a lot of time was the require-amdclean task, taking around 10 seconds even for adding just a single character like while working in the development environment. Migrating from Grunt to Gulp wasn't helping us since build time was nearly the same. Gaurav Nanda and I took a break from our daily chores and read many articles/blogs and the not-so-useful official docs to get a good command over various technologies. We were ready to spend some quality time in researching technologies which could fit in our build system.

Also, as I mentioned we didn't have a concrete build system it was the right time to investigate further. We had so many healthy discussions regarding improving things and thus we thought of upgrading our tech stack too. It was a great fit to be used as a standalone Javascript library, which is exactly our case.Įverything was working as expected but maintenance, performance, and scale were the issues.

#Npm upgrade webpack code

Get rid of file size/source code readability concerns.

Generation of single js file entirely in Vanilla JavaScript.

We didn't have to include require.js in production, thus, saving some bytes.

We had a number of tasks like the require-amdclean task, concatenating different script / CSS files, minification of files, cache-busting mechanism and so on.įollowing are some benefits we were getting from the require-amdclean task: Grunt was being used for automating different tasks required to speed up mundane work. All the different modules were having their own require-config.js file to define rules for a particular module. Require.js was being used for good code-structuring, managing modules and their loading. Also, there was no concrete build system which could be scaled upon adding new components. The project has a huge code-base and has many independent components inside it with some shared utilities. For the past couple of years, we have been using require.js for module loading and Grunt for automating tasks on front-end, for one out of many projects we have in Wingify.