ignite: ignite-cli does not play well with symlinks
Linked npm packages are not available as boilerplate
You can try this by using a npm linked package or even by replacing the ignite-{yourBoilerplateName} folder by a symlink.
Create a boilerplate plugin, link it then try to ignite a new app with that boilerplate
#Linking result
/home/libre/.nvm/versions/node/v8.2.1/lib/node_modules/ignite-AutoRnApp ->
/home/libre/dev/AutoRnApp/ignite/plugins/ignite-AutoRnApp
# Then ignite the app
libre@libre:~/dev$ ignite new BoilerTest -b ignite-AutoRnApp #Also tried without "ignite-" prefix
🔥 igniting app BoilerTest
✖ ignite-AutoRnApp is not available on npm.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
We also searched in these directories:
libre@libre:~/dev$ ignite doctor
System
platform linux
arch x64
cpu 4 cores Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
directory /home/libre/dev
JavaScript
node 8.2.1 /home/libre/.nvm/versions/node/v8.2.1/bin/node
npm 5.3.0 /home/libre/.nvm/versions/node/v8.2.1/bin/npm
yarn 0.27.5 /home/libre/.nvm/versions/node/v8.2.1/bin/yarn
React Native
react-native-cli 2.0.1
Ignite
ignite 2.0.0 /home/libre/.nvm/versions/node/v8.2.1/bin/ignite
Android
java 1.8.0_131 /usr/bin/java
android home - /home/libre/Android/Sdk
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (7 by maintainers)
Just tested this with master and it’s working great, a huge improvement for plugin authors. Thanks again.
ok, PR is in to
fs-jetpack. He’s cutting a new version. Next step is for me to bump that dependency version on https://github.com/infinitered/gluegun .Then we’ll be set to bask in glorious symlinks my friends.
(unlikely to get to this until the weekend tho)
Alright, hopefully https://github.com/szwacz/fs-jetpack/pull/55 will be accepted. Then we can add this.
I tested this workflow locally and it seems to be what we need. 🎉