Cli-microsoft365: Accessing non-existent property '_theme' message shown in CLI output

Created on 15 Dec 2020  路  14Comments  路  Source: pnp/cli-microsoft365

Description

I noticed when you run the latest version of the CLI you are getting an output like this when executing commands.

(node:18312) Warning: Accessing non-existent property '_theme' of module exports inside circular dependency
(Use node --trace-warnings ... to show where the warning was created)

image

Steps to reproduce

  • Install the cli on a new machine
  • run any command

Expected result

  • the output is not showing this error message

Actual result

image

Environment

  • Windows 10
  • Windows Server 2019
question waiting on response
Source
picture plamber

Most helpful comment

Can confirm this. Issue fixed in next release. Closing the issue.

picture plamber on 22 Dec 2020
🎉2

All 14 comments

Have you updated dependencies by executing npm i after pulling the latest source?

waldekmastykarz picture waldekmastykarz on 15 Dec 2020

Made a fresh installation yesterday on a customers device with this result:
image

Noticed the same error today on my dev environment.

plamber picture plamber on 15 Dec 2020

Could you please try installing @next to see if the issue still persists?

waldekmastykarz picture waldekmastykarz on 15 Dec 2020

Uninstalled it and installed it with @next. Same issue

plamber picture plamber on 15 Dec 2020

Working for me in Docker.

image

What does node -v return?

garrytrinder picture garrytrinder on 15 Dec 2020

Just discovered the same issue on my end with version 3.3.0 and 3.4.0. Think it might be related to node version 14. Going to test it out on version 12.

estruyf picture estruyf on 18 Dec 2020
👍2

Node version 12 on Windows btw, seems to fix it. Don't have the issue when running it on macOS. Might be Windows related.

estruyf picture estruyf on 18 Dec 2020
👍2

It was an issue with v3.3.0 and Node@14 on macOS. @StfBauer updated markshell and the issue seems to be fixed in v3.4.0 preview on Node@14 on macOS. I'll check Windows

waldekmastykarz picture waldekmastykarz on 18 Dec 2020
❤1

I can reproduce the issue but only with v3.3.0 (@latest) on Node@14 on Windows. v3.3.0 on Windows an macOS works fine with Node@12. v3.4.0 (@next) also doesn't show this error on Node@14 on both macOS and Windows.

waldekmastykarz picture waldekmastykarz on 18 Dec 2020
👍1

Latest beta on Linux (alpine) using Node@14 is also working fine, so does indeed seem to be only Windows related.

image

garrytrinder picture garrytrinder on 18 Dec 2020
👍2

Not sure if this is entirely Windows related, I just got the _theme error on Ubuntu 20.04 LTS in WSL2.

@pnp/[email protected]
node@14

image

garrytrinder picture garrytrinder on 19 Dec 2020

Correct: as I mentioned, the issue is visible in v3.3.0 on Node@14 on al OSes.

waldekmastykarz picture waldekmastykarz on 19 Dec 2020
👍1

@plamber are our observations correct and can you use v3.3.0 on Node@12 or v3.4.0 (beta) on Node@14 without the warning?

waldekmastykarz picture waldekmastykarz on 22 Dec 2020

Can confirm this. Issue fixed in next release. Closing the issue.

plamber picture plamber on 22 Dec 2020
🎉2
Was this page helpful?
0 / 5 - 0 ratings

Related issues

thomyg picture thomyg  路  3Comments
vineet2907 picture vineet2907  路  3Comments
VelinGeorgiev picture VelinGeorgiev  路  3Comments
plamber picture plamber  路  3Comments
waldekmastykarz picture waldekmastykarz  路  3Comments