I have an implementation in sage10 which is using the following code to pass some variables to a javascript: bundle('foo')->enqueue()->localize('fooAjax', ['ajaxurl' => admin_url('admin-ajax.php'), 'nonce' => wp_create_nonce('foo_check_nonce')]); Is there a way to achieve that with vite?

[image] Where is the hot reloading dev site when using Vite? sage Related to this new Vite approach, how does one localize a script now that the Bud bundle('app')->enqueue()->localize method is gone? setup.php now injects with the wp_head hook rather than wp_enqueue_scrip…

I would go with a different approach. I enqueue my scripts in a separate file/s, based on the volume of the project. There i would do something like that: add_action(‘wp_enqueue_scripts’, function () { $style = Vite::asset('resources/css/survey/survey.css'); $script = Vite::asset('resourc…

I’m still not clear on this solution. The link seems to suggest moving the enqueue out of admin_head filter, but I’m fairly new to Vite, so could someone provide more details? As with the original question, I’m trying to get Ajax working on the front end of my WP site.

The REST API has been in WordPress for almost a decade. Y’all really shouldn’t be using admin-ajax… As far as “localizing” scripts goes in Sage 11/Vite – just output the JS you need. Several approaches have been shown. What have you tried?

Thanks for responding. In app.js, I have the AJAX call, so it is loaded automatically by Sage: $.ajax({ type: 'POST', url: frontend_ajax_object.ajaxUrl, data: {action: 'event_month'}, dataType:"json", success: function …

There aren’t any enqueued assets in Sage 11. wp_localize_script requires using a handle that is enqueued. Personally I would ignore @hristolaskov ’s post on this topic. Follow the solution in this topic for your answer. Just output the JS you need on the front-end — there’s several different ways t…

How to use enqueue()->localize() in vite/sage11

vite

mikespainhower April 10, 2025, 2:00pm 2