Vitaly Peretiatko

Just found a solution - you have to install it using `npm install --arch=x64`, and it runs perfectly using Rosetta 2.

@pxpm I don't have a real use case for changing key, found this bug when working on server-side export operation and did tests to make sure it works with all...

@tabacitu @pxpm hate to tell it to you, but after that PR problem with ->key() is still there: ``` protected function setupListOperation() { CRUD::column('fluid')->key('fluid')->label('Fluid'); CRUD::column('fluid')->key('fluid_1')->label('Fluid 1'); CRUD::column('fluid')->key('fluid_2')->label('Fluid 2'); ``` Shows...

I think the easiest solution is to only allow to set key in the constructor as a second optional parameter: ``` CRUD::column('name', 'key'); ```

@tabacitu before that for my test I just manually applier PR to sources in /vendor/backpack/crud, after a message from @pxpm thought "oh, maybe there are other changes that I don't...

This helped me: ``` resolve: { alias: { handlebars: 'handlebars/dist/handlebars.min.js' } } ```

> Looks like it's here now: https://github.com/viperet/vscode-sftp-revived > > But it too hasn't had responses in a while. Anyone find any alternatives/revived versions? I just made a fork to fix...

@jcellon please post full log. Does it correctly detects Magento root location? Does it finds some modules/themes/blocks? "File not in the workspace (not saved yet?)" means just what it says...

Hi @WebKenth, most of the MagentoWizard's functions require Magento 2 files, so VSCode workspace folder should contain Magento 2 install for it to work correctly. As I understand you have...

Hello @ljr95, can you try to put full absolute path to your ./php script in the "magentoWizard.tasks.php" parameter?