Grunt theme source files missing when running Grunt execGetting an issue working with Grunt in Magento...
How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?
Pythonic way to find the last position in a string not matching a regex
Will a top journal at least read my introduction?
How to figure out whether the data is sample data or population data apart from the client's information?
Minimum value of 4 digit number divided by sum of its digits
How to stop co-workers from teasing me because I know Russian?
Were there two appearances of Stan Lee?
In gnome-terminal only 2 out of 3 zoom keys work
Is creating your own "experiment" considered cheating during a physics exam?
Is there a way to get a compiler for the original B programming language?
Can not tell colimits from limits
Reverse the word in a string with the same order in javascript
Has any spacecraft ever had the ability to directly communicate with civilian air traffic control?
Phrase for the opposite of "foolproof"
How to verbalise code in Mathematica?
What's the metal clinking sound at the end of credits in Avengers: Endgame?
Why is the origin of “threshold” uncertain?
Will tsunami waves travel forever if there was no land?
Confusion about capacitors
Illegal assignment from SObject to Contact
Help, my Death Star suffers from Kessler syndrome!
Examples of non trivial equivalence relations , I mean equivalence relations without the expression " same ... as" in their definition?
Why didn't this hurt this character as badly?
Stop and Take a Breath!
Grunt theme source files missing when running Grunt exec
Getting an issue working with Grunt in Magento 2Magento 2 Theme - grunt watch with overridden {module}.scssMagento Grunt Less Compilation behaves weirdProblem with extending Luma theme using Grunt with Lessinstall npm for Magento 2 on a system the runs Plesk Onyx without deleteing Plesklocal grunt database errors, when I have a vagrant magento2 boxGrunt watch doesn't watch _theme.less and custom less file(Magento2) Grunt Less problem with a new themeImport new custom less files after grunt configurationMagento 2 Theme Development - grunt watch not detecting changes of custom LESS file
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have a theme that extends the Luma theme. I am trying to get Grunt working to do preprocessing. So far, I don't have any changes/additions in my theme at all. I setup my themes.js as follows:
module.exports = {
...
training_test: {
area: 'frontend',
name: 'Training/test',
locale: 'en_US',
files: [
'css/styles-m',
'css/styles-l'
],
dsl: 'less'
}
};
I do not have any root source files, but the documentation states that if you do not have any, use those from the parent theme.
When I run grunt exec:training_test
I get the following error message:
Processed Area: frontend, Locale: en_US, Theme: Training/test, File type: less.
>> [InvalidArgumentException]
>> Verify entered values of the argument and options. Unable to resolve the source file for 'frontend/Training/test/en_US/css/styles-m.less'
>>
I setup Grunt using a build script (on Ubuntu, hence the symlink):
sudo apt-get -y install nodejs
sudo apt-get -y install npm
sudo npm install -g grunt-cli
sudo ln -s /usr/bin/nodejs /usr/bin/node
cd /var/www/html/public; npm install
I then ran the magento deploy task (not sure if this is required or not):
bin/magento dev:source-theme:deploy
I noticed that the Luma theme also does not extend the source files in question (css/styles-m, css/styles-l):
luma: {
area: 'frontend',
name: 'Magento/luma',
locale: 'en_US',
files: [
'css/styles-m',
'css/styles-l'
],
dsl: 'less'
},
Could it be an issue of multiple theme inheritance?
magento-2.1 grunt magento-2.1.4
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a theme that extends the Luma theme. I am trying to get Grunt working to do preprocessing. So far, I don't have any changes/additions in my theme at all. I setup my themes.js as follows:
module.exports = {
...
training_test: {
area: 'frontend',
name: 'Training/test',
locale: 'en_US',
files: [
'css/styles-m',
'css/styles-l'
],
dsl: 'less'
}
};
I do not have any root source files, but the documentation states that if you do not have any, use those from the parent theme.
When I run grunt exec:training_test
I get the following error message:
Processed Area: frontend, Locale: en_US, Theme: Training/test, File type: less.
>> [InvalidArgumentException]
>> Verify entered values of the argument and options. Unable to resolve the source file for 'frontend/Training/test/en_US/css/styles-m.less'
>>
I setup Grunt using a build script (on Ubuntu, hence the symlink):
sudo apt-get -y install nodejs
sudo apt-get -y install npm
sudo npm install -g grunt-cli
sudo ln -s /usr/bin/nodejs /usr/bin/node
cd /var/www/html/public; npm install
I then ran the magento deploy task (not sure if this is required or not):
bin/magento dev:source-theme:deploy
I noticed that the Luma theme also does not extend the source files in question (css/styles-m, css/styles-l):
luma: {
area: 'frontend',
name: 'Magento/luma',
locale: 'en_US',
files: [
'css/styles-m',
'css/styles-l'
],
dsl: 'less'
},
Could it be an issue of multiple theme inheritance?
magento-2.1 grunt magento-2.1.4
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a theme that extends the Luma theme. I am trying to get Grunt working to do preprocessing. So far, I don't have any changes/additions in my theme at all. I setup my themes.js as follows:
module.exports = {
...
training_test: {
area: 'frontend',
name: 'Training/test',
locale: 'en_US',
files: [
'css/styles-m',
'css/styles-l'
],
dsl: 'less'
}
};
I do not have any root source files, but the documentation states that if you do not have any, use those from the parent theme.
When I run grunt exec:training_test
I get the following error message:
Processed Area: frontend, Locale: en_US, Theme: Training/test, File type: less.
>> [InvalidArgumentException]
>> Verify entered values of the argument and options. Unable to resolve the source file for 'frontend/Training/test/en_US/css/styles-m.less'
>>
I setup Grunt using a build script (on Ubuntu, hence the symlink):
sudo apt-get -y install nodejs
sudo apt-get -y install npm
sudo npm install -g grunt-cli
sudo ln -s /usr/bin/nodejs /usr/bin/node
cd /var/www/html/public; npm install
I then ran the magento deploy task (not sure if this is required or not):
bin/magento dev:source-theme:deploy
I noticed that the Luma theme also does not extend the source files in question (css/styles-m, css/styles-l):
luma: {
area: 'frontend',
name: 'Magento/luma',
locale: 'en_US',
files: [
'css/styles-m',
'css/styles-l'
],
dsl: 'less'
},
Could it be an issue of multiple theme inheritance?
magento-2.1 grunt magento-2.1.4
I have a theme that extends the Luma theme. I am trying to get Grunt working to do preprocessing. So far, I don't have any changes/additions in my theme at all. I setup my themes.js as follows:
module.exports = {
...
training_test: {
area: 'frontend',
name: 'Training/test',
locale: 'en_US',
files: [
'css/styles-m',
'css/styles-l'
],
dsl: 'less'
}
};
I do not have any root source files, but the documentation states that if you do not have any, use those from the parent theme.
When I run grunt exec:training_test
I get the following error message:
Processed Area: frontend, Locale: en_US, Theme: Training/test, File type: less.
>> [InvalidArgumentException]
>> Verify entered values of the argument and options. Unable to resolve the source file for 'frontend/Training/test/en_US/css/styles-m.less'
>>
I setup Grunt using a build script (on Ubuntu, hence the symlink):
sudo apt-get -y install nodejs
sudo apt-get -y install npm
sudo npm install -g grunt-cli
sudo ln -s /usr/bin/nodejs /usr/bin/node
cd /var/www/html/public; npm install
I then ran the magento deploy task (not sure if this is required or not):
bin/magento dev:source-theme:deploy
I noticed that the Luma theme also does not extend the source files in question (css/styles-m, css/styles-l):
luma: {
area: 'frontend',
name: 'Magento/luma',
locale: 'en_US',
files: [
'css/styles-m',
'css/styles-l'
],
dsl: 'less'
},
Could it be an issue of multiple theme inheritance?
magento-2.1 grunt magento-2.1.4
magento-2.1 grunt magento-2.1.4
edited Feb 22 '17 at 20:07
Laura
asked Feb 20 '17 at 19:25
LauraLaura
2,12012045
2,12012045
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 8 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I don't know if it's the case, but try to setup your theme settings with real file names on themes.js. For example, if you set "css/styles-m" and "css/styles-l", create less files in your theme.
While your theme has <parent>Magento/luma</parent>
in theme.xml, it has inherited all styles.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f160866%2fgrunt-theme-source-files-missing-when-running-grunt-exec%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't know if it's the case, but try to setup your theme settings with real file names on themes.js. For example, if you set "css/styles-m" and "css/styles-l", create less files in your theme.
While your theme has <parent>Magento/luma</parent>
in theme.xml, it has inherited all styles.
add a comment |
I don't know if it's the case, but try to setup your theme settings with real file names on themes.js. For example, if you set "css/styles-m" and "css/styles-l", create less files in your theme.
While your theme has <parent>Magento/luma</parent>
in theme.xml, it has inherited all styles.
add a comment |
I don't know if it's the case, but try to setup your theme settings with real file names on themes.js. For example, if you set "css/styles-m" and "css/styles-l", create less files in your theme.
While your theme has <parent>Magento/luma</parent>
in theme.xml, it has inherited all styles.
I don't know if it's the case, but try to setup your theme settings with real file names on themes.js. For example, if you set "css/styles-m" and "css/styles-l", create less files in your theme.
While your theme has <parent>Magento/luma</parent>
in theme.xml, it has inherited all styles.
answered Mar 17 '17 at 12:27
GediminasGediminas
361114
361114
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f160866%2fgrunt-theme-source-files-missing-when-running-grunt-exec%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown