Installing local packages with Meteor - meteor

I'm going through some Meteor tutorials trying to get up to speed, seems like a nice framework. However I'm having difficulty, perhaps because I'm overcomplicating things, with packages. I've installed iron-router and set up some routes, simple enough, apart from that the package is linked to from my projects route rather than being installed into my projects folder structure - I installed with mrt - and iron-router is serving the templates in it's examples folder. Deleting that folder kills the app. Manually installing irk-router into the packages folder for my project and ensuring smart.json is linking to it does nothing to help.
I've ready and searched for hours now but I'm guessing I'm doing something very off the wall as I can't see anyone else with this issue.
Are packages always global in the ./meteorite folder and linked to, or are they local? And if so how do you set them up?
Cheers.
EDIT: After some more tinkering I believe the issue is actually iron-router and not the local install. The app runs but I just have a white screen, I think iron-router is not able to locate my templates.

In the end I removed all the packages, manually deleted anything left over, and re-installed them with Meteorite. That was the only way to fix the problem.

cd /usr/local/meteor/lib/ && npm install <module>

Related

ASP.NET - install React and typescript

So have created an ASP.NET 4.5.2 project and now need to install react and typescript. I installed node.js so wondering if its best to install via that. Also because I will be using TypeScript I will need the .d.ts files is there an easy way to install these in the project locally? Cause I assume everything else will be installed globally by npm as I might use them in other projects?
One other thing I am confused by all the different types of react packages available on npm, do i need a few or just one of them? I have worked on many projects involving this kind of tech stack but they are established and have never created one from scratch like i am doing now. So some really informative links or tips here would be immensely helpful! :)
So using Visual Studio 2017 I followed this tutorial and managed to get it working. The only issue left now is that i need to call webpack cmd on the project root when i make changes before refreshing the site. I am fine with this and will look into further into automating it as it kind of is a different and unrelated question.
One thing I will include is to always install npm packages globally (most of the time anyway) and just link them in using npm link. Was quite useful considering I went through the process a few times creating the project from scratch over and over again until I understood it all.

Dart Packages folder not existing anymore how do I integrate with symfony now for development

Back in the times of dart 1.9.x I made a dart frontend with symfony rest backend. Today I wanted to setup a development environment to do some more work on that app.
Unfortunately it turned out that dart 1.21.x does no longer create a packages folder where all the dart files are. This not only breaks the way integration worked up until now for development but it also breaks how template Urls are resolved by anything other than pub serve
Appart from creating the packages folder symlinks myself or completely rewriting the App. Does anybody know a good way to integrate the latest dart with Symfony?
You can opt-in
pub get --packages-dir
but the option is planned to be removed eventually, therefore try to find a way your application works without it.
The migration to code generation, DDC, and bazel might make this easier (none released yet)
There are also the packages
https://pub.dartlang.org/packages/package_resolver
https://pub.dartlang.org/packages/package_config
that help with the .packages file that replaces the packages directory and symlinks.
The sass package (which most often causes issues with the missing packages directory) also should become available in a version that doesn't depend on the packages directory soon.

Bower_components in grunt and Git

Hello all I'm after general opinions here.
My scenario is that when I'm building websites or web apps I tend to use grunt or gulp as a task runner. I drop in my dev dependencies via the help of bower and I'm using GIT for my version control.
In my repo I have a post-receive hook that exports repo to another folder on server that is accessible for previewing via http.
During the development phase I have all files/folders etc split into a nice MVC pattern but these can get compiled/minified into a single file with a task I have listed in my grunt file. I do this at staging/production, but for development /debugging i keep it all separated.
What's the best way to cater for the bower_components folder with GIT. I want them exported onto server but not sure that I need to be tracking them through GIT as they are maintained by their own authors.
Any thoughts or ideas would be great.
There are few opinions about adding bower_components to the git.
To keep in git:
+ "No strange issues with backend-team". I don't know why, but from time to time somebody has problems like "I just do bower install and nothing work". (I think this happens because somebody make bower install -F when others do just without -F flag)
Not to keep:
- There is no point to keep libs history. Seriously.
- Once I'm saw the issue when one guy cannot even pull from git(windows) just because somebody make bower instal jquery --save and bower instal jQuery --save (on linux). There were 2 folders (jquery and jQuery) which windows cannot resolve

gruntjs: do I need to install dependency plugins for each project?

I am recently using gruntjs. It's amazing. I am using version 0.4.5
Every time when I am going to create a new project, do I need to install all dependency plugins that I needed? like grunt-contrib-uglify, grunt-contrib-sass etc.
Basically, I use 4-5 plugins for each project and just wonder to know that if there is away to use it globally.
Going through grunt doc, they said I have to install dependencies locally, that means all plugins for each project?
:(

How To Clean a Development Build of a Meteorjs App?

There are two command line programs to start/stop/manage your meteor app. There is meteor and there is mrt. As of the latest build (0.8.2 or so) it's really not clear what the difference is between these two, if any. Both seem to support the argument "help" like meteor help and mrt help. The output of both seems to be the same to me.
Sadly, I do not see a "clean" argument available when I check the help for either of these. What do I need to do if I want to achieve a clean build? One that would
Blow away all packages and re-install them
Blow away any compiled templates
Blow away all Sass/Less compiled output
I ask this because I find myself in some kind of dependency Hades right now and want out now.
Meteor is still in a pre-release state. So the idea of packages is (still as of this post) not officially supported, though it will be soon. The meteor community stepped in to build their own way to use 3rd party packages and this is what meteorite does.
Most of the commands you give to meteorite are eventually passed to meteor which is why you see the same output.
The only (main difference is) mrt add which checks atmospherejs.com for packages first.
These two will be merged very soon (there is a branch on meteor on github called packaging which seeks to achieve this)
The idea of 'clean' isn't really there in meteor because most of the stuff is based on hot code reloads, so when a file changes its completely scrapped/(cleaned) and rewritten.
If you change a bit of code it will rebuild all this unless you have a syntax error.
Nonetheless if you want to 'clean' the build from everything you would have to do this in two steps (the meteor part and the meteorite part)
This erases some stuff in the hidden .meteor folder
meteor reset
Delete everything in ~/.meteorite/packages
Delete all symlinks only in your projects /packages folder. Be careful not to delete the folders because these will have been put in by you/whoever made your project and wouldn't be from atmosphere or meteor
Then run mrt update to reinstall all the atmosphere packages from scratch

Resources