Force include node_modules in package? - npm

I want to npm publish my dist dir that looks like this:
dist
├── README.md
├── node_modules
│   └── clap
│   └── dist
│   └── es
│   ├── index.js
│   └── index.js.map
├── package.json
...
└── utils
├── memory-stream.js
├── memory-stream.js.map
├── mysql-users.js
├── mysql-users.js.map
├── sql.js
├── sql.js.map
├── utils.js
└── utils.js.map
Notice how there's a node_modules dir in there. I want to publish that along with everything else.
The files in there are compiled, but they're part of a local package not distributed on npm, so I do want it bundled.
My code references it like this:
var index = require('../node_modules/clap/dist/es/index.js');
So it should work perfectly fine.
The problem is that it looks like npm publish has it hardcoded to ignore directories called node_modules. Is there any way to override that behaviour?

Related

Expo: console.log stopped showing up

SDK Version: 45
Platforms(Android/iOS/web/all): iOS
Add the appropriate "Tag" based on what Expo library you have a question on.
My managed expo project suddenly stopped showing console.log on terminal when I run expo run:ios.
Also, auto bundling on file changes also stopped.
The following is the version information I get when I run npm list.
├── #babel/core#7.18.10
├── #primer/primitives#7.9.0
├── #react-native-async-storage/async-storage#1.17.9
├── #react-native-firebase/analytics#15.3.0
├── #react-native-firebase/app#15.3.0
├── #react-native-firebase/auth#15.3.0
├── #react-native-firebase/firestore#15.3.0
├── #react-navigation/bottom-tabs#6.3.2
├── #react-navigation/native-stack#6.7.0
├── #react-navigation/native#6.0.11
├── #sanity/client#3.3.3
├── #shopify/restyle#2.1.0
├── #types/flat#5.0.2
├── #types/lodash#4.14.184
├── #types/react-native#0.66.21
├── #types/react#17.0.48
├── dotenv#16.0.1
├── expo-apple-authentication#4.2.1
├── expo-av#11.2.3
├── expo-build-properties#0.2.0
├── expo-dev-client#1.0.1
├── expo-splash-screen#0.15.1
├── expo-status-bar#1.3.0
├── expo#45.0.8
├── flat#5.0.2
├── lodash#4.17.21
├── react-dom#17.0.2
├── react-native-pager-view#5.4.15
├── react-native-reanimated#2.8.0
├── react-native-safe-area-context#4.2.4
├── react-native-screens#3.11.1
├── react-native-web#0.17.7
├── react-native#0.68.2
├── react#17.0.2
└── typescript#4.3.5
I solved this problem by upgrading expo sdk from 45 to 46 by executing expo-cli upgrade.
To find more information about expo sdk migration: please refer to "Upgrading your app" section of this post.

webpack load amd path modules dependency

I am testing the loading of modules in webpack. How would you indicate the path of the dependency in an AMD module?
My project has something like this:
├── modules
│   ├── mod1.js
│   ├── mod2.js
│   └── others
│   └── mod3.js
├── public
│   └── bundle.js
├── src
│   └── app
│   └── app.js
└── webpack.config.js
in app.js I import only mod3.js therefore you must compile the three JS (mod1, mod2, mod3) since mod3.js depend on them.
I have a "others" route. Every time I create a folder I have to include the following line in webpack.config.js?
path.resolve(__dirname, 'modules/others'),
Is it not possible to indicate the path of the dependency in the module itself without webpack compiling go to the hard defined in the config?
Thank you

IntelliJ import subfolder as project

Having a code structure like below which contains documentation at the root level how can I TELL IDEA to import the Code/spark subfolder as a project?
.
├── Code
│   ├── foo
│   │   ├── bar
│   │   └── baz
│   └── spark
│   ├── build.sbt
│   ├── common
│   ├── job1
│   ├── project
│   ├── run_application
│   ├── sbt
│   ├── scalastyle-config.xml
│   └── version.sbt
├── Docs
You need to add Content Root, go to Project Structure settings (Ctrl + Alt + Shift + s), select your module, then on the right panel click Add Content Root and select Docs folder. Then you can select it and mark as part of the Module, for documentation I believe it should be Resources.
Even better: use a proper build tool like gradle and then apply https://docs.gradle.org/current/userguide/composite_builds.html

Change modules loading priority

I would like to know the right way to change modules loading priorities in Linux. I want to have hdmi and LCD output the most quickly.
For now it take 3 seconds to came, I know it's not delay due to hdmi or TV because the first stuff I see on screen is some lines about mali init (mali is the name of the GPU here).
I use a A10-Olinuxino-Lime board with an homemade rootfs generated using buildroot and a custom Linux made for this kind of processor (linux-sunxi).
The tree of /etc/:
etc/
├── dhcp
│   ├── dhclient.conf
│   └── dhcpd.conf
├── dropbear
├── fstab
├── group
├── hostname
├── hosts
├── init.d
│   ├── rcK
│   ├── rcS
│   ├── S01logging
│   ├── S20urandom
│   ├── S40network
│   ├── S50dropbear
│   ├── S80dhcp-relay
│   ├── S80dhcp-server
│   ├── S80mali
│   └── S99TVOS
├── inittab
├── inittab~
├── inputrc
├── issue
├── ld.so.cache
├── ld.so.conf
├── ld.so.conf.d
├── mtab -> /proc/mounts
├── network
│   ├── if-down.d
│   ├── if-post-down.d
│   ├── if-post-up.d
│   ├── if-pre-down.d
│   ├── if-pre-up.d
│   ├── if-up.d
│   └── interfaces
├── nsswitch.conf
├── os-release
├── passwd
├── profile
├── protocols
├── random-seed
├── resolv.conf -> ../tmp/resolv.conf
├── securetty
├── services
├── shadow
├── ts.conf
└── wpa_supplicant.conf
Do you have any ideas ?
I'd create an /etc/init.d/S00modules script containing a sequence of insmod (or modprobe if your env supports it) lines.
If that doesn't help, then your modules are loaded even earlier,and you'll have to find how and where that happens. I'd first look at /sbin/init or what is used instead.

rails3 asset pipeline and file collisions

I'm updating an existing rails 2 app to rails 3, and having some trouble understanding the asset pipeline. I have read through the guide and as I understand it, files in any of the following directories will resolve to /assets:
app/assets
lib/assets
vendor/assets
and you could access them using helpers...i.e.
image_tag('logo.png')
But what I don't understand is how collisions are handled? For example, what if there are the following files:
app/assets/images/logo.png
lib/assets/images/logo.png
If I go to myapp.com/assets/images/logo.png, which file will be returned? I could check for collisions manually within my app, but this becomes a pain point when using gems that rely on the asset pipeline.
Based on what I've found, you can't have duplicate files, as rails will just return the first one found.
This seems like a bit of a design flaw, as a gem may not namespace their own assets
Why not taking advantage of the index manifest and organize your app/assets into decoupled modules? You can then reference to a particular image, image_tag('admin/logo.png'), and get for free your UI codebase organised in a more meaningful way. You could even promote a complex component, such as Single Page Application into it's own module and reuse it from different parts of the app.
Let's say you app is composed out of three modules: the public side, an admin UI and, e.g., a CRM to let your agents track the selling process at your company:
app/assets/
├── coffeescripts
│   ├── admin
│   │   ├── components
│   │   ├── index.coffee
│   │   └── initializers
│   ├── application
│   │   ├── components
│   │   ├── index.sass
│   │   └── initializers
│   └── crm
│   ├── components
│   ├── index.sass
│   └── initializers
├── images
│   ├── admin
│   ├── application
│   └── crm
└── stylesheets
├── admin
│   ├── components
│   └── index.sass
├── application
│   ├── components
│   └── index.sass
└── crm
├── components
└── index.sass
21 directories, 6 files
Don't forget to update your application.rb so they will be precompiled properly:
config.assets.precompile = %w(admin.js application.js crm.js
admin.css application.css crm.css)