If I use npm for openfl, will haxe install in each node_modules folder?

VishwasGagrani · November 27, 2022, 7:28am

I see some support of haxe for npm.
However I have experienced that npm creates node_modules folder in each project. And that contains the framework folders.
Does that mean if I use npm for haxe, and package.json mentions haxe, neko etc and dependencies, they will be installed in each project inside node_modules folder?

My concern is that this folder itself is too big and takes up much space on harddisk.

Right now I am not using npm and haxe is globally installed so it’s not an issue.

Reference:

github.com

openfl/openfl-samples-haxe/blob/master/demos/PiratePig/package.json

{
  "name": "org.openfl.samples.piratepig-haxe",
  "version": "1.0.0",
  "private": true,
  "devDependencies": {
    "actuate": "^1.8.8",
    "haxe": "^5.0.10",
    "haxe-loader": "^0.5.0",
    "openfl": "^8.6.1",
    "uglifyjs-webpack-plugin": "^1.3.0",
    "webpack": "^4.20.2",
    "webpack-cli": "^3.1.2",
    "webpack-dev-server": "^3.1.9",
    "webpack-merge": "^4.1.4"
  },
  "haxeDependencies": {
    "haxe": "3.4.7"
  },
  "scripts": {
    "build": "npm run build:prod",

This file has been truncated. show original

VishwasGagrani · November 27, 2022, 2:40pm

Update:
I tried using npm from here:

And as I guessed node_modules folder is 212MB in size. That won’t be practical to be used in every project folder. Maybe there is a way to use single node_modules folder in all projects.

However now my question is - What happened to project.xml ? How would I use it while using npm?