Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: unknown definition for mixin named box-shadow

  1. #1
    Sencha Premium Member
    Join Date
    Jan 2016
    Posts
    13

    Default unknown definition for mixin named box-shadow

    Hi,

    I upgraded ExtJS from 6.0.2 to 6.2.0 and I upgraded Sencha CMD to the latest version at the same time.

    I went into my package and did an upgrade:

    Code:
    sencha -sdk ../../../ext package upgrade
    Now, when I try to build a package, I get this error:


    Code:
    sencha package build
    [INF] Building C:\cygwin\home\XXXX\webui\packages\local\PDFPanel\build\PDFPanel-all-debug.scss to C:\cygwin\home\XXXX\webui\packages\local\PDFPanel\build\resources\PDFPanel-all-debug.css
    [LOG] Building C:/cygwin/home/XXXX/webui/packages/local/PDFPanel/build/PDFPanel-all-debug.scss
    [ERR] unknown definition for mixin named box-shadow : C:/cygwin/home/XXXX/webui/ext/packages/core/sass/etc/recipes/color.scss:178
    [ERR] unknown definition for mixin named text-shadow : C:/cygwin/home/XXXX/webui/ext/packages/core/sass/etc/recipes/color.scss:181
    [LOG] Build error for C:/cygwin/home/XXXX/webui/packages/local/PDFPanel/build/PDFPanel-all-debug.scss
    [ERR] Sass compilation encountered 2 error(s)
    [ERR] [email protected]://platform/fashion-phantomjs.js:5:10951
    [email protected]://code/phantom-sass-compiler.js:106:30
    [email protected]://platform/fashion-phantomjs.js:5:782
    [email protected]://platform/fashion-phantomjs.js:2:47711
    phantomjs://platform/fashion-phantomjs.js:2:26241
    [email protected]://platform/fashion-phantomjs.js:4:2874
    [email protected]://platform/fashion-phantomjs.js:2:26136
    [email protected]://code/phantom-sass-compiler.js:111:26
    global [email protected]://code/phantom-sass-compiler.js:153:10
    Exiting with code 3
    [email protected]://platform/fashion-phantomjs.js:5:10951
    [email protected]://code/phantom-sass-compiler.js:106:30
    [email protected]://platform/fashion-phantomjs.js:5:782
    [email protected]://platform/fashion-phantomjs.js:2:47711
    phantomjs://platform/fashion-phantomjs.js:2:26241
    [email protected]://platform/fashion-phantomjs.js:4:2874
    [email protected]://platform/fashion-phantomjs.js:2:26136
    [email protected]://code/phantom-sass-compiler.js:111:26
    global [email protected]://code/phantom-sass-compiler.js:153:10
    [ERR]
    [ERR] BUILD FAILED
    [ERR] com.sencha.exceptions.ExBuild: PhantomJS sass build exited with code : 3
    [ERR]   at org.apache.tools.ant.dispat
    [ERR] ch.DispatchUtils.execute(DispatchUtils.java:106)
    [ERR]
    [ERR] Total time: 23 seconds
    [ERR] The following error occurred while executing this line:
    C:\cygwin\home\XXXX\webui\packages\local\PDFPanel\.sencha\package\build-impl.xml:187: The following error occurred while executing this line:
    C:\cygwin\home\XXXX\webui\packages\local\PDFPanel\.sencha\package\sass-impl.xml:265: The following error occurred while executing this line:
    C:\cygwin\home\XXXX\webui\packages\local\PDFPanel\.sencha\package\sass-impl.xml:206: The following error occurred while executing this line:
    C:\cygwin\home\XXXX\webui\packages\local\PDFPanel\.sencha\package\sass-impl.xml:241: com.sencha.exceptions.ExBuild: PhantomJS sass build exited with code : 3

  2. #2
    Sencha Premium Member
    Join Date
    Jan 2016
    Posts
    13

    Default

    By the way, here is my package.json:


    Code:
    {
        /**
         * The name of the package.
         */
        "name": "PDFPanel",
    
    
        /**
         * Alternate names for this package.
         *
         *    "alternateName": [],
         */
    
    
         /**
          * The namespace of this package.
          *
          * As a general rule, all classes that belong to this package should be under this namespace
          * if multiple namespaces are part of this package, set this to "".
          */
         "namespace": "PDFPanel",
    
    
        /**
         * The package type.
         *
         * Sencha Cmd understands the following types of packages:
         *  - code : An arbitrary package of code for use by applications or other packages.
         *  - theme : A package to be used as an application's theme.
         *  - locale : A package containing localization strings or locale-specific code.
         *  - template : A package containing one or more templates.
         */
        "type": "code",
    
    
        /**
         * The toolkit used by this theme (only for "theme" package type).
         *
         * Themes can specify the toolkit they apply to ("classic" or "modern").
         *
         *    "toolkit": "classic",
         */
        "toolkit": "classic",
    
    
         /**
          * The author of the package.
          *
          * Required only if you are distributing this package through a Sencha Cmd repository,
          * in which case it should match the name you assign to your local package repository.
          */
        "creator": "anonymous",
    
    
        /**
         * A summarized description of this package.
         */
        "summary": "Short summary",
    
    
        /**
         * A detailed description of this package.
         */
        "detailedDescription": "Long description of package",
    
    
        /**
         * The package version.
         *
         * Typically, changes to the package should come along with changes to the version.
         * This number should be in this format: d+(.d+)*
         */
        "version": "1.0.0",
    
    
        /**
         * The version that users can transparently update from without requiring code changes.
         *
         * In addition the version property, packages can also indicate the degree to which
         * they are backward compatible using the compatVersion property.
         */
        "compatVersion": "1.0.0",
    
    
        /**
         * Spec. version of this package.json file.
         * This is set automatically by Sencha Cmd when first generating this file
         */
        "format": "1",
    
    
        /**
         * Additional resources used during theme slicing operations
         */
        "slicer": {
            "js": [
                {
                    "path": "${package.dir}/sass/example/custom.js",
                    "isWidgetManifest": true
                }
            ]
        },
    
    
        /**
         * Controls the output directory.
         */
        "output": "${package.dir}/build",
    
    
        /**
         * Indicates whether this is a locally developed package or downloaded form a repository.
         * Defaults to true on newly generated packages, should not be changed.
         */
        "local": true,
    
    
        /**
         * The theme (package) this package will use (e.g., "ext-theme-neptune", etc.).
         * This is only needed if the built package will be used by a non-Cmd application.
         *
         *     "theme": "ext-theme-classic",
         */
    
    
        /**
         * Sass configuration properties.
         */
        "sass" : {
            /**
             * The namespace to which this package's SASS corresponds. The default value of
             * "PDFPanel" means that the files in ./sass/src (and ./sass/var) match classes in
             * the PDFPanel" root namespace. In other words, "PDFPanel.panel.Panel" maps to
             * ./sass/src/panel/Panel.scss.
             *
             * To style classes from any namespace, set this to blank. If this is blank,
             * then to style "PDFPanel.panel.Panel" you would put SASS in
             * ./sass/src/PDFPanel/panel/Panel.scss.
             */
            "namespace": "PDFPanel",
    
    
            /**
             * Comma-separated list of files or folders containing extra Sass. These
             * files are automatically included in the Sass compilation. By default this
             * is just "etc/all.scss" to allow import directives to control the order
             * other files are included.
             *
             * All "etc" files are included at the top of the Sass compilation in their
             * dependency order:
             *
             *      +-------+---------+
             *      |       | base    |
             *      | theme +---------+
             *      |       | derived |
             *      +-------+---------+
             *      | packages        |  (in package dependency order)
             *      +-----------------+
             *      | application     |
             *      +-----------------+
             */
            "etc": [
                "${package.dir}/sass/etc/all.scss"
             ],
    
    
            /**
             * Comma-separated list of folders containing Sass variable definitions
             * files. These file can also define Sass mixins for use by components.
             *
             * All "var" files are included after "etc" files in the Sass compilation in
             * dependency order:
             *
             *      +-------+---------+
             *      |       | base    |
             *      | theme +---------+
             *      |       | derived |
             *      +-------+---------+
             *      | packages        |  (in package dependency order)
             *      +-----------------+
             *      | application     |
             *      +-----------------+
             *
             * The "sass/var/all.scss" file is always included at the start of the var
             * block before any files associated with JavaScript classes.
             */
            "var": [
                "${package.dir}/sass/var"
            ],
    
    
            /**
             * Comma-separated list of folders containing Sass rule files.
             *
             * All "src" files are included after "var" files in the Sass compilation in
             * dependency order (the same order as "etc"):
             *
             *      +-------+---------+
             *      |       | base    |
             *      | theme +---------+
             *      |       | derived |
             *      +-------+---------+
             *      | packages        |  (in package dependency order)
             *      +-----------------+
             *      | application     |
             *      +-----------------+
             */
            "src": [
                "${package.dir}/sass/src"
            ]
        },
    
    
        /**
         * This is the comma-separated list of folders where classes reside. These
         * classes must be explicitly required to be included in the build.
         */
        "classpath": [
            "${package.dir}/src"
        ],
    
    
        /**
         * Comma-separated string with the paths of directories or files to search. Any classes
         * declared in these locations will be automatically required and included in the build.
         * If any file defines an Ext JS override (using Ext.define with an "override" property),
         * that override will in fact only be included in the build if the target class specified
         * in the "override" property is also included.
         */
        "overrides": [
            "${package.dir}/overrides"
        ],
    
    
        "example": {
            /**
             * One or more folders that contain example applications for this package.
             */
            "path": [
                "${package.dir}/examples"
            ]
    
    
            /**
             * You can list apps specifically.
             *
             *      "apps": [
             *          "demo1",
             *          "demo2"
             *      ]
             *
             * By default, all subfolders in the path are considered example applications.
             */
        },
    
    
        /**
         * The framework this package will use (i.e., "ext" or "touch").
         * This is only needed if the built package will be used by a non-Cmd application.
         *
         *     "framework": "ext",
         */
    
    
        /**
         * Packages can require other packages in the same way that applications can require
         * packages.
         *
         * Can be specified as an array of package names or configuration objects.
         *
         *      "requires": [
         *          "foo",
         *          "[email protected]",
         *          {
         *              "name": "baz"
         *              "version": "1.5"
         *          }
         *      ]
         *
         * Can also be specified as an object:
         *
         *      "requires": {
         *          "foo": "2.2",
         *          "bar": {
         *              "minVersion": "1.1",
         *              "version": "2.0"
         *          }
         *      }
         */
        "requires": []
    }

  3. #3
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985
    Answers
    506

    Default

    So you upgraded Cmd first, then Ext JS, then your application?

  4. #4
    Sencha Premium Member
    Join Date
    Jan 2016
    Posts
    13

    Default

    Not sure what "upgraded" means in your question. I installed the new version of ExtJS and installed the new version of Sencha CMD at the same time

    Then I ran "sencha -sdk ../../../ext package upgrade" and "sencha package build"

  5. #5
    Sencha User
    Join Date
    Sep 2016
    Posts
    2

    Default

    Any updates by this issue? I have the same problem

  6. #6
    Sencha Premium Member
    Join Date
    Jan 2015
    Location
    Austria
    Posts
    6

    Default

    Hi, I am facing the same problem. Any solutions up to now? Did anyone try to setup a complete new workspace/app and including their own source files?

  7. #7
    Sencha Premium Member
    Join Date
    Jan 2015
    Location
    Austria
    Posts
    6

    Default

    Just a quick status update:
    I fixed the problems i've been facing. My applications and packages are compiling again. I had to set the following properties in package.json for my packages:
    "toolkit": "classic",
    "theme": "theme-triton"

    This is only required if the package should be build on its own. If the package is part of the required block of an application(app.json), this is not necessary.

    The build process still outputs some warnings for missing resources like "Theme image not found: images/menu/default-menubar-checked.png", but that's something for sencha to fix. I will open a ticket soon, if there isn't already one.

    This solution worked for a complete new workspace and migrating the existing code. I did not test to update the old workspace to the new cmd and framework version. Just in case

  8. #8
    Sencha User ThorstenSuckow's Avatar
    Join Date
    Sep 2007
    Location
    Aachen, Germany
    Posts
    618

    Default

    Any news on this? I'm facing the same issues with v6.2.2.36

  9. #9
    Sencha Premium Member
    Join Date
    Jan 2016
    Posts
    13

    Default

    Quote Originally Posted by ThorstenSuckow View Post
    Any news on this? I'm facing the same issues with v6.2.2.36
    Make sure "framework" and "toolkit" are set in your package.json, that cleared up all my problems

  10. #10
    Sencha Premium Member
    Join Date
    May 2011
    Posts
    33

    Default

    In my case I also have to add "theme" to package.json or add "skip.sass=1" to sencha.cfg

Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 2
    Last Post: 4 Jul 2016, 6:52 AM
  2. App Build Unknown Definition Problem
    By mjcee in forum Sencha Cmd
    Replies: 3
    Last Post: 7 Apr 2016, 11:46 AM
  3. Replies: 2
    Last Post: 16 Dec 2015, 10:32 AM
  4. Unknown definition for dependency
    By sananda.dasgupta in forum Ext JS 6.x Q&A
    Replies: 2
    Last Post: 20 Jul 2015, 7:00 PM
  5. Replies: 6
    Last Post: 27 Aug 2014, 12:00 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •