I'm building fist mobile project by using react-native, expo and lerna. But I have problem with lerna. When I type: yarn install all packages. My problem is that lerna push all module packages in mobile package to the outside node_modules folder so that the script to run react native is not available in mobile package. My question is that there are any solutions for lerna to recognize those modules out of package mobile scope.
This is my folder structure
| my-project/
| ---- node_modules/
| -------- react-native/
| -------- lerna/
| -------- expo/
| ---- package.json
| ---- lerna.json
| ---- packages/
| -------- mobile/
| ------------ node_modules/
| ---------------- bin/
| ------------------- react-native
| ------------------- react-native.cmd
| ------------ package.json
Related
I have the following Web API solution structure with three projects in a .NET 5 Web Api
.
+-- Api.csproj
| +-- Dependencies
| | +-- Projects
| | | +-- Infrastructure.csproj
| | | | +-- Dependencies
| | | | | +-- Projects
| | | | | | +-- Core.csproj
| | | | | +-- Packages
| | | | | | +-- Serilog.Sinks.Telegram (2.0.1)
| | | | | | | +-- Newtonsoft.Json (11.0.2)
When I build Infrastructure.csproj, it succeeds, but 2 strange issues
Build warning Infrastructure.csproj : warning NU1603: Serilog.Sinks.TelegramClient 2.0.1 depends on Newtonsoft.Json (>= 10.0.0) but Newtonsoft.Json 10.0.0 was not found. An approximate best match of Newtonsoft.Json 10.0.1 was resolved.
Looking in the \debug folder, I don't see any dlls for Serilog or Newtonsoft.
When I build Api.csproj, it succeeds, but again strange issues
Build warning Infrastructure.csproj : warning NU1603: Serilog.Sinks.TelegramClient 2.0.1 depends on Newtonsoft.Json (>= 10.0.0) but Newtonsoft.Json 10.0.0 was not found. An approximate best match of Newtonsoft.Json 10.0.1 was resolved.
Build warning Api.csproj : warning NU1603: Serilog.Sinks.TelegramClient 2.0.1 depends on Newtonsoft.Json (>= 10.0.0) but Newtonsoft.Json 10.0.0 was not found. An approximate best match of Newtonsoft.Json 10.0.1 was resolved.
Looking in the \debug folder of the Api.csproj, I do see Serilog and Newtonsoft dlls.
The Newtonsoft dll in debug has a version of 12.0.3.*
My Questions:
Is it right that there are no Serilog or Newtonsoft dlls in Infrastructure.csproj output folder?
Why am I getting a warning about Newtonsoft for the Api.csproj build when the dll is correctly put into output folder and the version is greater than the warning?
When using yarn workspaces is it possible to have nested package.json files to resolve dependancies for a subset of packages? Avoiding repetition?
where cra are create-react-apps and pkg are packages that these sites consume.
e.g.
| /
| - package.json
|---- /sites
|-------- /cra-1
| - package.json
|-------- /cra-2
| - package.json
|---- /packages
| - package.json // <<---- Extra level here
|-------- /pkg-1
| - package.json
|-------- /pkg-1
| - package.json
|-------- /pkg-2
| - package.json
this would allow us to share common dependancies for our packages... keep them all in sync and up-to-date
hello i want to install 2 node_modules (other directory) only one command.
| - folderOne
| - node_modules
| - package.json // current directory
|
| - folderTwo
| - node_modules
for example.
when i write npm install in folderOne, same node_modules installed with both folderOne and folderTwo
or
| - folderOne
| - node_modules
| - package.json // current directory
|
| - folderTwo
| - node_modules
| - package.json // automatic installed
i want to write npm install in folderOne, npm install excute in folderTwo
how do that??
I have an electron app with the following structure
- dist
| - index.html
| - node_modules
| - nm (is an exact copy of node_modules)
- package.json
| ...
if I refer to the node modules in my index.html as node_modules/module the app won't find the module if built with the build command from electron-builder. But if I change that line in my index.html to nm/module it is perfectly willing to load it.
It seems to me that electron-builder isn't copying node_modules into the application, but I can't see why it would do that. Is it excluding all folders named node_modules and how can I fix this?
NPM publishes to Nexus under the dash "-" folder. Packages cannot be viewed using Browse Storage.
How to avoid the dash "-" folder?
Is there way to publish npm packages with the folder structure like NuGet?
Is it possible to have a structure like this?
PRIVATE_NPM/
|
|--package-1.0.0/
| |
| |--package-1.0.0.tgz
|
|--package-1.0.1/
|
|--package-1.0.1.tgz
The repository structure in Nexus is standard, and the "-" is part of that standard, it's used to retrieve metadata.
There is a declined feature request (Nexus 2.10) for an NPM package browsing UI.