Packer Config Error for env.keys.themeId

[fatihturan]

Hi,

When I try to start Packer with packer start command I see an error with Error: [packer-config]: A value has not been defined for the key ‘env.keys.themeId’. Where should I define the themeId value?

[mrpacman101]

@fatihturan
Hi, can you confirm you have filled out this file?

When you use packer start - it will use "development" env by default.

Also i spotted Error:
This is a live theme!

I am not sure if this flag works with packer start --allow-live

Usually i don't use published live theme to edit, also on my development stores.

[fatihturan]

I filled the packer.env.json with private Shopify app id and password like this:

By the way I tried the Packer with different computer on Node 14.15.2 and its give error related with Babel:

[hayes0724]

For live themes you need to add --allowLive Command Docs

or

live setting in config

{
    "development": {
      "id": "74500041118",
      "password": "ebd6ce7f27aae8cdafb8111a5b887b9",
      "store": "my-store-name.myshopify.com",
      "live": "true",
      "ignore": [
        "settings_data.json"
      ]
    }
}

Can you confirm id has a correct theme id from themes page in Shopify? You can also check theme id's by using packer theme:list

Also it would help to have this info:

• Any flags used, example packer start --env=live
• OS: [e.g. Windows 10, Ubuntu, OSX]
• Node Version [e.g. 14.15.1]
• NPM Version [e.g. 6.14.8]
• Browser [e.g. chrome, safari]
• Packer Version [e.g. 1.2.1]

[fatihturan]

I tried the Packer on the another MacBook Pro M1. I entered the required values into packer.env.json file. I am able to list themes and create a sample theme like this:

Also I installed the packages with npm install command. But when I use the packer start I get the following errors:

System Info:

• macOS Big Sur 11.3.1 / MacBook Pro M1
• Node 16.2.0
• NPM 7.14.0
• Safari 14.1
• Packer v2.2.0

[mrpacman101]

@fatihturan I know it may not be related to this particular issue but i used npm before a lot - tho since latest MacOS updates i always got issues specifically on MacOS.
Since then i switched to "yarn" and cannot complain at all, it is working like a charm no issues at all.
Maybe worth a try.

[fatihturan]

I switched to Yarn. Removed the node_modules folder. And re-installed with yarn install command like below. But unfortunately, I still got the same errors:

Is it related to that compatibility issue on M1 architecture? Especially for fibers package?