Skip to content
Nathan Walker edited this page Mar 13, 2019 · 3 revisions

Why is there a package.json in some libs?

​ For scss package imports across shared code and projects. ​

Why is there a file:libs/scss dependency in root package.json?

​ For convenient shared SASS usage throughout. If you look inside xplat/web/scss/_variables.scss you will see @import '~@workspace/scss/common'; (substitute workspace with your name). This allows your web specific shared SASS to consume the entire workspace (cross platform) SASS from libs easily. ​

Why is there a references.d.ts file in root of workspace?

​ This allows full intellisense support across rich iOS/Android api's made available via NativeScript in your shared code in xplat/nativescript. ​

When running web app I get a SASS error?

​ You might experience this issue: ​

ERROR in ./node_modules/css-loader?{"sourceMap":false,"import":false}!./node_modules/postcss-loader/lib?{"ident":"postcss","sourceMap":false}!./node_modules/sass-loader/lib/loader.js?{"sourceMap":false,"precision":8,"includePaths":[]}!./xplat/web/scss/_index.scss
Module build failed: 
@import '~@[your workspace name]/scss/index';
^
      File to import not found or unreadable: ~@[your workspace name]/scss/index.

​ You just need to install root dependencies: npm install in the root of your workspace.

You can’t perform that action at this time.