You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I am a backend dev trying to build a react app, so I don't have much frontend knowledge.
A project I'm using has this library as a dependency, and when I try to npm start or npm run build after I pulled new changes, already existing *.scss.d.ts files are not updated, resulting in errors Property ... does not exist on type .... If I delete the generated file, new file is generated with all the latest fields.
This only happens if a class in scss was added, changing styles on existing classes doesn't trigger this. I see that there's a new class in scss, but there's no new property in generated file.
Webpack config is divided into dev and prod with export default from base config.
Also, is there a way not to use these generated files in production for example?
Hello! I am a backend dev trying to build a react app, so I don't have much frontend knowledge.
A project I'm using has this library as a dependency, and when I try to
npm start
ornpm run build
after I pulled new changes, already existing *.scss.d.ts files are not updated, resulting in errorsProperty ... does not exist on type ...
. If I delete the generated file, new file is generated with all the latest fields.This only happens if a class in scss was added, changing styles on existing classes doesn't trigger this. I see that there's a new class in scss, but there's no new property in generated file.
Webpack config is divided into dev and prod with
export default
from base config.Also, is there a way not to use these generated files in production for example?
package.json
webpack config
The text was updated successfully, but these errors were encountered: