Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I am working on 2-3 react apps, and for each app when I run npm install, it installs a bunch of dependencies in the "node-module" folder which is approximately 250-300mb in size! It becomes really hard to deploy that on Github. Is there any way to reduce file size of node_module folder.
You don't need to push node modules to github, they should be included in your .gitignore file.
Within the root directory, edit .gitignore and add the line
node_modules/
Now when you push to github, the node_modules directory will be ignored.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
Question is related to javascript project which uses node and web pack.
I see in my current project there is node_module -> lib folder , there is xyz.js file in lib folder.
And in dist folder of node_module there is xyz.amd.js & xyz.main.js & respective js.map
I would like to know what is difference between amd & main.js files
And how the Current project which contains this node_module folder uses these files.
If you can point me to any site/tutorial explaining these. it would be helpfull
node.js will load those modules from local the node_modules/ directorywhen it encounters statements such as:
var xyz = require("xyz");
Or
import xyz from 'xyz';
"amd" refers to the Asynchronous Module Definition API, which loads modules in a lazy fashion (i.e. as needed). I suspect your xyz.amd.js module is for the AMD loader.
https://github.com/amdjs/amdjs-api/wiki/AMD
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
I know dist folder is used for production, distribution and what it should contain.
What i want to know is, when is the best time to use it? in what kind of work environment/project requirement i should use dist folder? like Heroku, what are the other platforms where i can deploy an app without dist and the platforms where i can't deploy without it (if there is any)?
I'm new to this, if someone can clearify the process would be very much helpful.
The dist folder is for production website it's not necessary to have it. It will contain for example your image, css, script, vendor folder ready for production (minified and concatenated).
You can check on google for this. Type "how to deploy a production React app to Heroku" for example.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
Maybe I am doing it wrong. I want to do changes in node_modules folder. Now when I run npm run watch or npm run dev it doesn't get reflected in UI.
Any idea what is wrong?
Try editing from the /dist folder of the library you are trying to edit. Your changes will not reflect if you edit from the source and not from the output bundles.
Note: If you are just logging a result (via console.log) that is fine, but as much as possible, do not edit from the node_modules folder.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I'm using Nuxt.js 1.2 in my project, but I want to update it to latest version. How to do it? What needs to be considered when updating the version?
Simply run: yarn upgrade nuxt#^2.3.2
As stated here:
Please note that for upgrading Nuxt.js just changing version inside
package.json is not enough. Please use yarn upgrade or npm upgrade so
that the final directory structure of node_modules will be correct. In
case of problems clean up node_modules and
yarn.lock/package-lock.json.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have gone thru the intern-tutorial which is a very simple unit test case. However, it's not clear to me if the directory structure can be different and how flexible intern's configuration can be to accommodate it.
I'd like to find a tutorial that showed the v1.1 intern locations expected... which locations are mandatory and which can be modified and how that impacts the config file (intern.js) settings. What is the directory structure intern expects for a project and what is changeable, such as when you have multiple packages even.
In particular I'd like to see the relative location relationships of the:
web root
intern dir
intern.js config file
unit-test files
dojo/dijig/dojox/etc package location
modules in a package
Please show how placement relates to the configuration settings if possible.
As of Intern 1.1, the only thing that is mandatory is that Intern be installed as an npm dependency of the root project being tested. There are no relationships to any of the things you asked about, except that everything needs to be within the project’s root directory.