getting module not found error when running npm start

Developer Support
1

Hi there, I’m receiving this error message when running npm start:

ERROR in ./src/components/plasmic/basil_site_2_0/PlasmicFooter.jsx 25:0-99
Module not found: Error: Can't resolve './PlasmicGlobalVariant__Screen' in 'C:\Users\username\Documents\GitHub\git-repo\src\components\plasmic\plasmic-project=folder'

I’ve tried deleting node_modules folder + package-lock.json and reinstalling.
The site is made with plain React and the project ID is: w8Gkq37ZXmVbqHV15DJUBW

2

Hi Theo,
I just copied the project and sync down the code using the same React CodeGen approach and it works fine for me. Can you please check if a file with the name PlasmicGlobalVariant__Screen exists in the component/plasmic directory.

3

Hi @zonal_mammal thanks so much for looking.
looking at the PlasmicGlobalVariant__Screen in another project, i see that it’s deprecated.
Should I/how should I go about removing it in plasmic.json?

 *  @deprecated Plasmic now uses a custom hook for Screen variants, which is
 *  automatically included in your components. Please remove this provider
 *  from your code.
 */

export function ScreenVariantProvider(props) {
  console.warn(
    "DEPRECATED: Plasmic now uses a custom hook for Screen variants, which is automatically included in your components. Please remove this provider from your code."
  );
  return props.children;
}
4

I think this is more of a note for users who have already implemented their logic using Provider approach. If so, they can migrate their logic to the custom hook. If you don’t have such logic implemented in your project, you can completely ignore this warning.

You can safely remove the ScreenVariantProvider function from this file.

5

@zonal_mammal thank you