Cannot see changes in Magento 2 js and css

Cannot see changes in Magento 2 js and css

October 11, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Cannot see changes in Magento 2 js and css

Debugging Magento 2 CSS and JavaScript Issues

If you’re new to Magento development, it’s common to encounter frustrating situations where your custom JavaScript and CSS files aren’t rendering as expected, despite being properly loaded in the source code. Let me guide you through a systematic approach to resolve this issue.

Step 1: Understanding Magento’s Asset Management

Magento 2 has a sophisticated asset management system that handles minification, concatenation, and versioning of JavaScript and CSS files. When you make changes to your custom files (located in app/design/frontend/Vendor/ThemeName/web/js and web/css), the system may not immediately reflect those updates due to its caching mechanisms.

Step 2: Clearing Cache: The Right Way

You mentioned that you’ve cleared both the backend cache and disabled all caches, which is a good start. However, let’s ensure we’re using the correct commands:

bin/magento cache:clean

This command cleans all cache types, including layout, block HTML output, and collections.

If your issue persists after running this command, it might be due to Magento’s built-in browser caching mechanisms that prevent your changes from being seen. To bypass this:

  1. Open the pub/static directory in your project.
  2. Delete the contents of the pub/static folder recursively:
rm -rf pub/static/*
  1. Run the deployment command with the clean flag to regenerate static files:
bin/magento setup:static-content:deploy clean

Step 3: Checking Your JavaScript and CSS Files

Ensure that your custom JavaScript file (custom.js) is properly imported in a layout XML file. For example, if you want the script to load on the homepage only, add this to app/design/frontend/Vendor/ThemeName/Magento_Theme/layout/default.xml:

<referenceBlock name="head.additional">
    <block class="Magento\Framework\View\Element\Template" template="Vendor_Module::custom.phtml"/>
</referenceBlock>

In the custom.js file, make sure you’re using Magento’s mixin system correctly. For example:

require([
    'jquery',
    'jquery-ui-modules-easing'
], function($) {
    // Your JavaScript code here
});

Step 4: Checking Your CSS File

Similarly, your custom CSS file (custom.css) should be imported in a layout XML file or an .html file within the theme’s directory.

<referenceContainer name="head.container">
    <block class="Magento\Framework\View\Element\Template" template="Vendor_Module::custom.phtml"/>
</referenceContainer>

In your CSS file, ensure you’re using the correct syntax and that the selectors are properly targeting the elements you intend to style.

Conclusion

Debugging Magento 2’s asset management can be challenging for beginners. The key lies in understanding the system’s caching mechanisms and ensuring proper importation of your custom files in the layout XML files or .html files within your theme directory.

If you’re still facing issues, I recommend checking the Laravel Company blog for more advanced Magento 2 development tips and tricks. The pub/static folder can also be configured to use a different deployment mode that may resolve your issue.

Remember, patience is key when working with large-scale e-commerce platforms like Magento 2. By following these steps and understanding the system’s architectural quirks, you’ll become proficient in handling CSS and JavaScript issues efficiently.

Magento 2 Cache Themes Admin

Our network