Unexpected token export when running npm test

[voitanos]

Unexpected token export when running npm test

[andrewconnell]

Thanks... I can repo. Investigating...

[andrewconnell]

Update - I understand why this is happening, but I can't figure out how to fix it for a bigger set of circumstances.

It's easy to fix for just the one library you're using, but this will quickly turn into a +1 issue when someone uses another library, so I'm looking for a more dynamic solution... this is affecting all three of my presets...

Still working...

[petecuttriss]

Understood. Have a merry Christmas Andrew! Thanks again for your all help.

[andrewconnell]

Something occurred to me: What you're trying to do won't give you desirable results. You're trying to use the Environment & EnvironmentType objects that won't yield desirable results outside of a SharePoint context.

You should be able to just add the following in your spec file to tell Jest to mock those two objects without any changes to the jest config file:

jest.mock('@microsoft/sp-core-library/', () => {
  return {
    'Environment': {},
    'EnvironmentType': {},
  };
});

I'm going to close this issue for now, but still working on a more robust solution in the case where it appears as an issue in other projects.

[taranxd]

I am facing the similar issue and writing the above code didn't fix the issue :(

[andrewconnell]

@taranxd please open a new issue with more details to better track the issue.

I became aware these presets are not working with the latest SPFx and need to investigate the root cause. Learned about the issue this week so will look into it shortly...

[jmunozcastro]

Hello @andrewconnell, I am working implementing jest in some SPFx projects and I get the same error that explain @petecuttriss, the difference is that I am working with SPFx Framework v1.11 Do you have found another solution @andrewconnell or @petecuttriss? I appreciate so much the help ;)