Title: @import doesn’t work Last modified: March 9, 2022 --- # @import doesn’t work * Resolved [may1937](https://wordpress.org/support/users/may1937/) * (@may1937) * [4 years, 1 month ago](https://wordpress.org/support/topic/import-doesnt-work-12/) * Hello, Diana. * [@import](https://wordpress.org/support/users/import/) has been unavailable since last month. Was there any change in specifications? * It seems that [@import](https://wordpress.org/support/users/import/) will be abolished from October 2022. Is there anything to do with it? * I would appreciate it if you could tell me. Viewing 5 replies - 1 through 5 (of 5 total) * Plugin Author [SilkyPress](https://wordpress.org/support/users/diana_burduja/) * (@diana_burduja) * [4 years, 1 month ago](https://wordpress.org/support/topic/import-doesnt-work-12/#post-15440874) * What do you mean by [@import](https://wordpress.org/support/users/import/) “has been unavailable”? Could you tell me exactly what you’re trying to do and what doesn’t work? Are you talking about the plugin’s feature to import custom codes or are you trying to use the CSS [@import](https://wordpress.org/support/users/import/) directive in a custom code and it doesn’t work? * And in which way doesn’t it work? Do you get an error? * Where is it written that the [@import](https://wordpress.org/support/users/import/) will be abolished from October 2022? * At the moment I’d appreciate a bit of context for your questions. - This reply was modified 4 years, 1 month ago by [SilkyPress](https://wordpress.org/support/users/diana_burduja/). * Thread Starter [may1937](https://wordpress.org/support/users/may1937/) * (@may1937) * [4 years, 1 month ago](https://wordpress.org/support/topic/import-doesnt-work-12/#post-15447975) * See this for the deprecation of [@import](https://wordpress.org/support/users/import/). Is this an issue unrelated to this plugin? * [https://sass-lang.com/blog/the-module-system-is-launched](https://sass-lang.com/blog/the-module-system-is-launched) * The fact that [@import](https://wordpress.org/support/users/import/) cannot be used means that the file specified by [@import](https://wordpress.org/support/users/import/) cannot be read. After that, the CSS written in the SASS syntax is output as plain text, and it is not compiled into a proper CSS. What I’m trying to read with [@import](https://wordpress.org/support/users/import/) is a file that summarizes @mixins and constants, but it seems that the cause is that it becomes undefined because it can not be read. No errors or warnings will be displayed when updating. If you remove [@import](https://wordpress.org/support/users/import/), it will work properly. * [1earthsangha](https://wordpress.org/support/users/1earthsangha/) * (@1earthsangha) * [3 years, 8 months ago](https://wordpress.org/support/topic/import-doesnt-work-12/#post-15869116) * [@import](https://wordpress.org/support/users/import/) is being replaced by [@use](https://wordpress.org/support/users/use/) and [@forward](https://wordpress.org/support/users/forward/). But, even as a Pro user, I can’t get either of these, nor [@import](https://wordpress.org/support/users/import/), to work. * Please advise. * Thank you. * Plugin Author [SilkyPress](https://wordpress.org/support/users/diana_burduja/) * (@diana_burduja) * [3 years, 8 months ago](https://wordpress.org/support/topic/import-doesnt-work-12/#post-15872902) * The [@import](https://wordpress.org/support/users/import/) directive can be used inside a custom CSS/SASS code by defining an “ID” for the SASS custom code that needs to be imported (ex: vars.scss) and then using that ID as follows: * [@import](https://wordpress.org/support/users/import/) ‘vars.scss’; * in the SASS custom code that needs to import the other custom code. * If that doesn’t work, would you please make a few screenshots with the two custom SASS codes (the one that needs to be imported and the one where it needs to be imported) along with their options, so that I could try to replicate your usecase exactly on my test website and see what is wrong? * [1earthsangha](https://wordpress.org/support/users/1earthsangha/) * (@1earthsangha) * [3 years, 8 months ago](https://wordpress.org/support/topic/import-doesnt-work-12/#post-15875400) * An update from my side here: I got [@import](https://wordpress.org/support/users/import/) to work, although still having some issues with [@extend](https://wordpress.org/support/users/extend/). * Regarding the overall thread, it seems this plugin is using LibSass and not Dart Sass and only the latter [supports](https://sass-lang.com/documentation/at-rules/use) [@use](https://wordpress.org/support/users/use/) and [@forward](https://wordpress.org/support/users/forward/). I imagine it will be some effort to migrate from libsass (with perhaps the direct reliance from the plugin on sassphp?) to Dart, though it is [strongly encouraged](https://sass-lang.com/libsass). * I will report my issue with [@import](https://wordpress.org/support/users/import/) and [@extend](https://wordpress.org/support/users/extend/) in a separate thread. * Thanks! Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘@import doesn’t work’ is closed to new replies. * ![](https://ps.w.org/custom-css-js/assets/icon-128x128.png?rev=1303730) * [Simple Custom CSS and JS](https://wordpress.org/plugins/custom-css-js/) * [Frequently Asked Questions](https://wordpress.org/plugins/custom-css-js/#faq) * [Support Threads](https://wordpress.org/support/plugin/custom-css-js/) * [Active Topics](https://wordpress.org/support/plugin/custom-css-js/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/custom-css-js/unresolved/) * [Reviews](https://wordpress.org/support/plugin/custom-css-js/reviews/) ## Tags * [forward](https://wordpress.org/support/topic-tag/forward/) * [Import](https://wordpress.org/support/topic-tag/import/) * [use](https://wordpress.org/support/topic-tag/use/) * 5 replies * 3 participants * Last reply from: [1earthsangha](https://wordpress.org/support/users/1earthsangha/) * Last activity: [3 years, 8 months ago](https://wordpress.org/support/topic/import-doesnt-work-12/#post-15875400) * Status: resolved